Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c35332a6fc2413324e0c0f4955ad7fa2fbd537c6e2d47747e98c038a0336d0a

Tx prefix hash: 597b77df1079f847c04d77fdc169454f878051ad1d008cff4ffad3a7d027dec9
Tx public key: e2ddec1efb28a08b727b51a7bd7ab66fe870a377f4413c9bedc817bcd7c82171
Timestamp: 1724668299 Timestamp [UCT]: 2024-08-26 10:31:39 Age [y:d:h:m:s]: 00:231:06:54:11
Block: 1096251 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165177 RingCT/type: yes/0
Extra: 01e2ddec1efb28a08b727b51a7bd7ab66fe870a377f4413c9bedc817bcd7c8217102110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c49a415d03bf3829c144bb91a399b6ae849c3b013cbaa1ad0369ef9d5325f522 0.600000000000 1571438 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": 1096261, "vin": [ { "gen": { "height": 1096251 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c49a415d03bf3829c144bb91a399b6ae849c3b013cbaa1ad0369ef9d5325f522" } } ], "extra": [ 1, 226, 221, 236, 30, 251, 40, 160, 139, 114, 123, 81, 167, 189, 122, 182, 111, 232, 112, 163, 119, 244, 65, 60, 155, 237, 200, 23, 188, 215, 200, 33, 113, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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