Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20d6407259af5c4b4a161d92faf54cc9701f74042d665ac8a7bb2f7fd36e1a01

Tx prefix hash: b947c60f05c49d8b126c0b6f6d6abab03a78279155af3eeac875aedc6299061c
Tx public key: dc9f1403def61d91db57454c39afbe191bd2b37b14bb33f3d7dca9a4796ede06
Timestamp: 1712556098 Timestamp [UCT]: 2024-04-08 06:01:38 Age [y:d:h:m:s]: 01:038:14:25:02
Block: 995814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288589 RingCT/type: yes/0
Extra: 01dc9f1403def61d91db57454c39afbe191bd2b37b14bb33f3d7dca9a4796ede0602110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02837d2ebc0d8f4d5fcddd4b87ce574b343f10b7b749c9844baa73172f5d734f 0.600000000000 1456228 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": 995824, "vin": [ { "gen": { "height": 995814 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02837d2ebc0d8f4d5fcddd4b87ce574b343f10b7b749c9844baa73172f5d734f" } } ], "extra": [ 1, 220, 159, 20, 3, 222, 246, 29, 145, 219, 87, 69, 76, 57, 175, 190, 25, 27, 210, 179, 123, 20, 187, 51, 243, 215, 220, 169, 164, 121, 110, 222, 6, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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