Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c2715f9f620c1a5fc4f001fa21d7a765587eb62c4c1e35865c0b2887c280ebb

Tx prefix hash: 993d4f6d45673ad8f8dd83cd3acc0beb48988d3efb0191278b1b3432a3a6026a
Tx public key: 6e4bfea211807f86e1377d25b37980ff53b741b9cfecabb45ac04d97f53d6f80
Timestamp: 1740933990 Timestamp [UCT]: 2025-03-02 16:46:30 Age [y:d:h:m:s]: 00:264:07:41:37
Block: 1230640 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186667 RingCT/type: yes/0
Extra: 016e4bfea211807f86e1377d25b37980ff53b741b9cfecabb45ac04d97f53d6f800211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4050bdae07bf646831b2f84dc58328dd73c4a8c730fa1ceb5ffdf38de798ae59 0.600000000000 1717539 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": 1230650, "vin": [ { "gen": { "height": 1230640 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4050bdae07bf646831b2f84dc58328dd73c4a8c730fa1ceb5ffdf38de798ae59" } } ], "extra": [ 1, 110, 75, 254, 162, 17, 128, 127, 134, 225, 55, 125, 37, 179, 121, 128, 255, 83, 183, 65, 185, 207, 236, 171, 180, 90, 192, 77, 151, 245, 61, 111, 128, 2, 17, 0, 0, 0, 8, 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