Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7df82c65b9c8675f32b98d1693b8b08501da1649465e5c5debd73e9a50b0381

Tx prefix hash: 9313443dde11a30eaf0de7307f1777990c198e9786cb5456ee678ff6d5c94841
Tx public key: 8d481764811b4b2c22dce82863060eaf6c2d9ef75a1113217e09dc230f98d30c
Timestamp: 1709641040 Timestamp [UCT]: 2024-03-05 12:17:20 Age [y:d:h:m:s]: 01:104:19:43:17
Block: 971686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335831 RingCT/type: yes/0
Extra: 018d481764811b4b2c22dce82863060eaf6c2d9ef75a1113217e09dc230f98d30c02110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd389ba285ed2f3cdd06a59a85665d039a6e8734d50441a662dc6cd27270a6ae 0.600000000000 1431585 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": 971696, "vin": [ { "gen": { "height": 971686 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd389ba285ed2f3cdd06a59a85665d039a6e8734d50441a662dc6cd27270a6ae" } } ], "extra": [ 1, 141, 72, 23, 100, 129, 27, 75, 44, 34, 220, 232, 40, 99, 6, 14, 175, 108, 45, 158, 247, 90, 17, 19, 33, 126, 9, 220, 35, 15, 152, 211, 12, 2, 17, 0, 0, 0, 11, 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