Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9de729eabdb188201c1a3b25145ca6c52e19684517d0d9c6308c924f4c481b8

Tx prefix hash: 40170951054a6fe7f9fbc092b395fab5f59614129d5ab78328d3143310dd373f
Tx public key: 7468a22505a095b4f1eeb5a51b6ac3f44bcd26339209b4acf868eea90f47de10
Timestamp: 1717897905 Timestamp [UCT]: 2024-06-09 01:51:45 Age [y:d:h:m:s]: 00:228:17:03:24
Block: 1040133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163627 RingCT/type: yes/0
Extra: 017468a22505a095b4f1eeb5a51b6ac3f44bcd26339209b4acf868eea90f47de100211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd55a266654c4072f6fa6420102dfd4fb4168cec9125fcf2e4e4471c0ddfcb0b 0.600000000000 1508788 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": 1040143, "vin": [ { "gen": { "height": 1040133 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd55a266654c4072f6fa6420102dfd4fb4168cec9125fcf2e4e4471c0ddfcb0b" } } ], "extra": [ 1, 116, 104, 162, 37, 5, 160, 149, 180, 241, 238, 181, 165, 27, 106, 195, 244, 75, 205, 38, 51, 146, 9, 180, 172, 248, 104, 238, 169, 15, 71, 222, 16, 2, 17, 0, 0, 0, 5, 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