Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e24de102fbaaa1bed1920ec9767c4c5d2de44ca677fc4ae8a7f4ed58b9bd6a6

Tx prefix hash: 59f3f3933786f14337e634b0e81946d4b4983e170727b986f20abb24e1db938e
Tx public key: 2d311e0772acc5e5e1369b527f6b75d2339c213acfa847366c6e0647550be17f
Timestamp: 1746285667 Timestamp [UCT]: 2025-05-03 15:21:07 Age [y:d:h:m:s]: 00:267:18:51:20
Block: 1274953 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189009 RingCT/type: yes/0
Extra: 012d311e0772acc5e5e1369b527f6b75d2339c213acfa847366c6e0647550be17f021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: beda502fc96eb422798befde7e912a323604da4608f12fd4ccc2e4e751f2634d 0.600000000000 1762254 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 dinasty-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": 1274963, "vin": [ { "gen": { "height": 1274953 } } ], "vout": [ { "amount": 600000000, "target": { "key": "beda502fc96eb422798befde7e912a323604da4608f12fd4ccc2e4e751f2634d" } } ], "extra": [ 1, 45, 49, 30, 7, 114, 172, 197, 229, 225, 54, 155, 82, 127, 107, 117, 210, 51, 156, 33, 58, 207, 168, 71, 54, 108, 110, 6, 71, 85, 11, 225, 127, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8