Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e6cc320cd719070fa5d1c364430cb0e7e13a010aeed1359be378f8f42081f62

Tx prefix hash: 966a041d24694cb7656c2abf7419ef24eef63b2351ba4663cb044b9aa0840b2e
Tx public key: dfb150f54b8fcf6323eac83748b4ed76638c9bb9c20467b1a9753db46dacfa3b
Timestamp: 1729626616 Timestamp [UCT]: 2024-10-22 19:50:16 Age [y:d:h:m:s]: 00:032:11:33:26
Block: 1137332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23201 RingCT/type: yes/0
Extra: 01dfb150f54b8fcf6323eac83748b4ed76638c9bb9c20467b1a9753db46dacfa3b021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7dd1685485b3339b945072b465f1339187d54e4a845d6f6a86de2e3530fd057 0.600000000000 1620801 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": 1137342, "vin": [ { "gen": { "height": 1137332 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7dd1685485b3339b945072b465f1339187d54e4a845d6f6a86de2e3530fd057" } } ], "extra": [ 1, 223, 177, 80, 245, 75, 143, 207, 99, 35, 234, 200, 55, 72, 180, 237, 118, 99, 140, 155, 185, 194, 4, 103, 177, 169, 117, 61, 180, 109, 172, 250, 59, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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