Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f456f2dd4191ee48b8a6e75fcdf6b1f4efd822810969faf7e0d9df619a4cd6f8

Tx prefix hash: 5d38611c53792732b38493440572dd5ee5c8035fb0d1b5830a649d6abe64919f
Tx public key: e5d994a2359feca52c6fe5eae9ebb0cae65bba2ed38a747aedf6ae5917fea2ca
Timestamp: 1702402569 Timestamp [UCT]: 2023-12-12 17:36:09 Age [y:d:h:m:s]: 01:076:03:26:42
Block: 911685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315509 RingCT/type: yes/0
Extra: 01e5d994a2359feca52c6fe5eae9ebb0cae65bba2ed38a747aedf6ae5917fea2ca02110000000233af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c8b1e793df541ef03a6d82749deb36defe9df3de7f356591181f45bdb1509af 0.600000000000 1368901 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": 911695, "vin": [ { "gen": { "height": 911685 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c8b1e793df541ef03a6d82749deb36defe9df3de7f356591181f45bdb1509af" } } ], "extra": [ 1, 229, 217, 148, 162, 53, 159, 236, 165, 44, 111, 229, 234, 233, 235, 176, 202, 230, 91, 186, 46, 211, 138, 116, 122, 237, 246, 174, 89, 23, 254, 162, 202, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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