Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 09a20d431c334adeb692c3fae54044417382cbcf4bd4fb887c468cb40b8bbfe9

Tx prefix hash: 52614a989852f348cc1e5dc6d498e0d8ac38f3e88cc2aed96ed1c90d8cc08243
Tx public key: bf676f4b6e40c1d4ef21e40d40834de3560382e8d589fa659fafae2b2d109147
Timestamp: 1750055096 Timestamp [UTC]: 2025-06-16 06:24:56 Age [y:d:h:m:s]: 00:329:13:10:18
Block: 1306061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225477 RingCT/type: yes/0
Extra: 01bf676f4b6e40c1d4ef21e40d40834de3560382e8d589fa659fafae2b2d10914702110000000225a35a0f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: dcfd074fb9f8c87084781ac89916efdf73e5c6bc0368348a0433695a79ec4184 0.000600000000 1793664 of 15 -

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1306071, "vin": [ { "gen": { "height": 1306061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dcfd074fb9f8c87084781ac89916efdf73e5c6bc0368348a0433695a79ec4184" } } ], "extra": [ 1, 191, 103, 111, 75, 110, 64, 193, 212, 239, 33, 228, 13, 64, 131, 77, 227, 86, 3, 130, 232, 213, 137, 250, 101, 159, 175, 174, 43, 45, 16, 145, 71, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: