Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e3cd67c83dc0ab11d45fb1d48c34640fac0e0da44d93a6c8df3436c766d63cd

Tx prefix hash: 20c5495e3464108abc2693078d55447257cec5eae7111a3a5a7c88a18bd412d7
Tx public key: df35d9765a5d3c02e9f665a17ddb687e80586659d23d305c328d3fe6360cd4e0
Timestamp: 1729287013 Timestamp [UCT]: 2024-10-18 21:30:13 Age [y:d:h:m:s]: 01:016:11:31:02
Block: 1134549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270138 RingCT/type: yes/0
Extra: 01df35d9765a5d3c02e9f665a17ddb687e80586659d23d305c328d3fe6360cd4e00211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ce02487a26cd2c6c622a4555f4c7f3ca8b893121657d0c686458d2025a7c504 0.600000000000 1617870 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": 1134559, "vin": [ { "gen": { "height": 1134549 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ce02487a26cd2c6c622a4555f4c7f3ca8b893121657d0c686458d2025a7c504" } } ], "extra": [ 1, 223, 53, 217, 118, 90, 93, 60, 2, 233, 246, 101, 161, 125, 219, 104, 126, 128, 88, 102, 89, 210, 61, 48, 92, 50, 141, 63, 230, 54, 12, 212, 224, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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