Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcdf615254d7702c056705a42f57bb4ff930ca98ce7840e287d63f6a05514e9d

Tx prefix hash: db788a4046ba01f449d89ecea2cf27fecc4874ef4b4ac31b77d1d304cd3aa75f
Tx public key: fe78b9a3e0e6ad5a1144822d98e5c1059be768507090a913df396ed4686fce73
Timestamp: 1771784439 Timestamp [UTC]: 2026-02-22 18:20:39 Age [y:d:h:m:s]: 00:269:16:42:38
Block: 1483522 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198315 RingCT/type: yes/0
Extra: 01fe78b9a3e0e6ad5a1144822d98e5c1059be768507090a913df396ed4686fce73021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e4f2d3d8c81eb41dbd640187d2015e193e150266123042afa57158e2495ccb4d 0.000600000000 1972932 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": 1483532, "vin": [ { "gen": { "height": 1483522 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4f2d3d8c81eb41dbd640187d2015e193e150266123042afa57158e2495ccb4d" } } ], "extra": [ 1, 254, 120, 185, 163, 224, 230, 173, 90, 17, 68, 130, 45, 152, 229, 193, 5, 155, 231, 104, 80, 112, 144, 169, 19, 223, 57, 110, 212, 104, 111, 206, 115, 2, 17, 0, 0, 0, 2, 228, 245, 25, 63, 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: