Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2eadad4eb42ed527be0c65e62740a13e78f23d01bd2a9c16a52beb5740bbaa79

Tx prefix hash: 6dfa99f795727f00d64f3d26d4844b90f6a38bd41e4b66de36c33ff0ee17dcd8
Tx public key: 1bb020c0733a401e205435706e0148bdc1fb193add7f8e47ffd6a10f15cc5723
Timestamp: 1730624577 Timestamp [UCT]: 2024-11-03 09:02:57 Age [y:d:h:m:s]: 00:189:00:37:20
Block: 1145555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134951 RingCT/type: yes/0
Extra: 011bb020c0733a401e205435706e0148bdc1fb193add7f8e47ffd6a10f15cc57230211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c114c1bb5e302cd5db4c7e400d5166ea01daa5131c151b046eea1af940561118 0.600000000000 1630012 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": 1145565, "vin": [ { "gen": { "height": 1145555 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c114c1bb5e302cd5db4c7e400d5166ea01daa5131c151b046eea1af940561118" } } ], "extra": [ 1, 27, 176, 32, 192, 115, 58, 64, 30, 32, 84, 53, 112, 110, 1, 72, 189, 193, 251, 25, 58, 221, 127, 142, 71, 255, 214, 161, 15, 21, 204, 87, 35, 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