Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd3d719731b22145b0685361737fdb7166a63e1605c5a68b8c42cbcbabe037db

Tx prefix hash: 34395864626e3814444e87c3fe980a775fe0cb7c305e00940b4ca8d457f4ded1
Tx public key: 79b85394741f519f28e17f7e9826e3fcd19e83eeb99290cdc0e7069d363a5ede
Timestamp: 1699519219 Timestamp [UCT]: 2023-11-09 08:40:19 Age [y:d:h:m:s]: 01:015:21:13:08
Block: 887768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272717 RingCT/type: yes/0
Extra: 0179b85394741f519f28e17f7e9826e3fcd19e83eeb99290cdc0e7069d363a5ede021100000003679a8a81000000000000000000

1 output(s) for total of 0.702192340000 dcy

stealth address amount amount idx
00: ec1862e5ddde74dd1dc6356923fdc384ee3a0fdd3b32c93e89e1e38fe0787b9b 0.702192340000 1343667 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": 887778, "vin": [ { "gen": { "height": 887768 } } ], "vout": [ { "amount": 702192340, "target": { "key": "ec1862e5ddde74dd1dc6356923fdc384ee3a0fdd3b32c93e89e1e38fe0787b9b" } } ], "extra": [ 1, 121, 184, 83, 148, 116, 31, 81, 159, 40, 225, 127, 126, 152, 38, 227, 252, 209, 158, 131, 238, 185, 146, 144, 205, 192, 231, 6, 157, 54, 58, 94, 222, 2, 17, 0, 0, 0, 3, 103, 154, 138, 129, 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