Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f53c6995debce01e719d45434dd8cab74054f25a85c2d8c1b909b21205bfe494

Tx prefix hash: 768a793262a7e104738630da49c5b63c49028142aeaf56934fed05c3a6db77f0
Tx public key: 0b56a2a1ee4b35b80eb7fa826f6e0f3dc5847390082eb5c39e8e7085fad8f501
Timestamp: 1731490048 Timestamp [UCT]: 2024-11-13 09:27:28 Age [y:d:h:m:s]: 00:219:06:56:15
Block: 1152720 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156441 RingCT/type: yes/0
Extra: 010b56a2a1ee4b35b80eb7fa826f6e0f3dc5847390082eb5c39e8e7085fad8f501021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7e91fcc4182b01098fe12292997346bf36ba9804a4573270f5a948fab49674a 0.600000000000 1638323 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": 1152730, "vin": [ { "gen": { "height": 1152720 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7e91fcc4182b01098fe12292997346bf36ba9804a4573270f5a948fab49674a" } } ], "extra": [ 1, 11, 86, 162, 161, 238, 75, 53, 184, 14, 183, 250, 130, 111, 110, 15, 61, 197, 132, 115, 144, 8, 46, 181, 195, 158, 142, 112, 133, 250, 216, 245, 1, 2, 17, 0, 0, 0, 2, 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