Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bc3a74dd1f600d426d6021773bf99f627fd9eff78d65547e52f6b3341283b2d

Tx prefix hash: 7a0cffd6127f631a11fab4ee72bd2c69b7c0df98b8dfecbed804fc6bba40b860
Tx public key: e5ea6ed87afa070c04b73519ca0d8fd2af180483b8575f34875d4ee01fc36a71
Timestamp: 1772941660 Timestamp [UTC]: 2026-03-08 03:47:40 Age [y:d:h:m:s]: 00:255:08:52:58
Block: 1493104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188030 RingCT/type: yes/0
Extra: 01e5ea6ed87afa070c04b73519ca0d8fd2af180483b8575f34875d4ee01fc36a71021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fec6c295083722848bb9d991e0a577c7dd34887b152a23d3cebaef0252915cab 0.000600000000 1982658 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": 1493114, "vin": [ { "gen": { "height": 1493104 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fec6c295083722848bb9d991e0a577c7dd34887b152a23d3cebaef0252915cab" } } ], "extra": [ 1, 229, 234, 110, 216, 122, 250, 7, 12, 4, 183, 53, 25, 202, 13, 143, 210, 175, 24, 4, 131, 184, 87, 95, 52, 135, 93, 78, 224, 31, 195, 106, 113, 2, 17, 0, 0, 0, 3, 241, 136, 200, 168, 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: