Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 625d5a4becd414802f0f6a2c77db1973d2c5ccd4dcf06a1d1064da324016a661

Tx prefix hash: 7ae29461e86f2ef192612715895b14a1fe5f0d14db4031aa22b1462e0f419774
Tx public key: 586eed2b383bd717bdabfab5a2f744f547f828b962d54bef31150f7dcfe617bf
Timestamp: 1729479171 Timestamp [UCT]: 2024-10-21 02:52:51 Age [y:d:h:m:s]: 00:159:05:31:35
Block: 1136098 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113613 RingCT/type: yes/0
Extra: 01586eed2b383bd717bdabfab5a2f744f547f828b962d54bef31150f7dcfe617bf02110000000192627dee000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e95ca9a3e3be8f06af40e53b5bfcb4c9726a4ae407afaeee15c3cf6735eaf3e 0.600000000000 1619441 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": 1136108, "vin": [ { "gen": { "height": 1136098 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e95ca9a3e3be8f06af40e53b5bfcb4c9726a4ae407afaeee15c3cf6735eaf3e" } } ], "extra": [ 1, 88, 110, 237, 43, 56, 59, 215, 23, 189, 171, 250, 181, 162, 247, 68, 245, 71, 248, 40, 185, 98, 213, 75, 239, 49, 21, 15, 125, 207, 230, 23, 191, 2, 17, 0, 0, 0, 1, 146, 98, 125, 238, 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