Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7964859f9529695312f9a1a9f44d3a36e3d53c946afae393feca0badac720d43

Tx prefix hash: 8f4866cd52701b82f95d5279cdef7f5dcaa828724324f1b72f5d3e133d1159a2
Tx public key: ee32595554a1b74873f1d87f73a02ae6db88a3ce0374d3ab95bbeae8fe165f1e
Timestamp: 1722693603 Timestamp [UCT]: 2024-08-03 14:00:03 Age [y:d:h:m:s]: 00:247:14:42:55
Block: 1079877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176858 RingCT/type: yes/0
Extra: 01ee32595554a1b74873f1d87f73a02ae6db88a3ce0374d3ab95bbeae8fe165f1e021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39eaaac3ff80539e198bb2eef08d12f294b84a2cf0d16ed84b3ee4974b529ede 0.600000000000 1553022 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": 1079887, "vin": [ { "gen": { "height": 1079877 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39eaaac3ff80539e198bb2eef08d12f294b84a2cf0d16ed84b3ee4974b529ede" } } ], "extra": [ 1, 238, 50, 89, 85, 84, 161, 183, 72, 115, 241, 216, 127, 115, 160, 42, 230, 219, 136, 163, 206, 3, 116, 211, 171, 149, 187, 234, 232, 254, 22, 95, 30, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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