Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0f97fd0f44d61374e30e09c05272fa58165febb4c9c08083f685a3da06cee79

Tx prefix hash: 1b8d2d1394861d893b9e981095da2b62893ae6416b2a36e530b60f94217037e3
Tx public key: e22de08fcdda42b8d2aa81058cde92ca19832b737d027c253d9ba51b40b7846b
Timestamp: 1709542885 Timestamp [UCT]: 2024-03-04 09:01:25 Age [y:d:h:m:s]: 01:274:15:56:15
Block: 970869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 455049 RingCT/type: yes/0
Extra: 01e22de08fcdda42b8d2aa81058cde92ca19832b737d027c253d9ba51b40b7846b0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50efe303ed667ebfa873dcf411055866a8e911e8f613c5eeb56e4ca68077912c 0.600000000000 1430732 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": 970879, "vin": [ { "gen": { "height": 970869 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50efe303ed667ebfa873dcf411055866a8e911e8f613c5eeb56e4ca68077912c" } } ], "extra": [ 1, 226, 45, 224, 143, 205, 218, 66, 184, 210, 170, 129, 5, 140, 222, 146, 202, 25, 131, 43, 115, 125, 2, 124, 37, 61, 155, 165, 27, 64, 183, 132, 107, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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