Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02fbdebff41597ec0dcea58bb6287cd6241e745e41d9862c6a180e5080f4e6ae

Tx prefix hash: d7576d1cbf8e03fcb45f02e5c8a395aa09c9b115b1a1d2acf4a1d3229799cd48
Tx public key: 85fae54cb69b6c8e97d008065ffec664505981608adb29bfd63dcf0a3e2b5810
Timestamp: 1721201066 Timestamp [UCT]: 2024-07-17 07:24:26 Age [y:d:h:m:s]: 00:223:03:17:45
Block: 1067531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159349 RingCT/type: yes/0
Extra: 0185fae54cb69b6c8e97d008065ffec664505981608adb29bfd63dcf0a3e2b581002110000000ce914dd15000000000000000000

1 output(s) for total of 0.607800000000 dcy

stealth address amount amount idx
00: f37a6816f3d71c817248074d89d9191ee55e0af30db7eb883b7e19f3b7062cdf 0.607800000000 1538360 of 0

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": 1067541, "vin": [ { "gen": { "height": 1067531 } } ], "vout": [ { "amount": 607800000, "target": { "key": "f37a6816f3d71c817248074d89d9191ee55e0af30db7eb883b7e19f3b7062cdf" } } ], "extra": [ 1, 133, 250, 229, 76, 182, 155, 108, 142, 151, 208, 8, 6, 95, 254, 198, 100, 80, 89, 129, 96, 138, 219, 41, 191, 214, 61, 207, 10, 62, 43, 88, 16, 2, 17, 0, 0, 0, 12, 233, 20, 221, 21, 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