Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 893d3fa234c43d141ff8538697408a891c6470bc1b629e575e2562bd9f4cc68a

Tx prefix hash: bde4ab04985fc65e87745f53a617d9bba00eb32177a83e696e98089e6be8200a
Tx public key: 631e2a4b4d564de4f6748a1c1cf79a714d59c78e70317592f08d547e44e3e87d
Timestamp: 1717826242 Timestamp [UCT]: 2024-06-08 05:57:22 Age [y:d:h:m:s]: 00:364:02:19:40
Block: 1039537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260250 RingCT/type: yes/0
Extra: 01631e2a4b4d564de4f6748a1c1cf79a714d59c78e70317592f08d547e44e3e87d02110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4fe64d18665b583d66abfec880e50240a5957f69f9224a3c417a31250a628e4 0.600000000000 1508180 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": 1039547, "vin": [ { "gen": { "height": 1039537 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4fe64d18665b583d66abfec880e50240a5957f69f9224a3c417a31250a628e4" } } ], "extra": [ 1, 99, 30, 42, 75, 77, 86, 77, 228, 246, 116, 138, 28, 28, 247, 154, 113, 77, 89, 199, 142, 112, 49, 117, 146, 240, 141, 84, 126, 68, 227, 232, 125, 2, 17, 0, 0, 0, 9, 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