Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5deac0cf20490520b6e0f956241289a1dcddf803cd67b87d535b005e5c84216

Tx prefix hash: fd5cd57d87e95e54549a223b27b9bb524924add8bdee18e98199f882218d8e4b
Tx public key: 8eb26e76c96a66cefad951795652fc458f70e2f371c6955f02f4ed3df591e654
Timestamp: 1728137129 Timestamp [UCT]: 2024-10-05 14:05:29 Age [y:d:h:m:s]: 01:033:04:36:40
Block: 1125012 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282105 RingCT/type: yes/0
Extra: 018eb26e76c96a66cefad951795652fc458f70e2f371c6955f02f4ed3df591e65402110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1ae08d8bc23a690e13816cb92d9a1bd27a4a81a20254a7b58db14eab39d92c6 0.600000000000 1607685 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": 1125022, "vin": [ { "gen": { "height": 1125012 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1ae08d8bc23a690e13816cb92d9a1bd27a4a81a20254a7b58db14eab39d92c6" } } ], "extra": [ 1, 142, 178, 110, 118, 201, 106, 102, 206, 250, 217, 81, 121, 86, 82, 252, 69, 143, 112, 226, 243, 113, 198, 149, 95, 2, 244, 237, 61, 245, 145, 230, 84, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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