Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86d18848e75eb51c9c13ea11d409e242f54514b70c32baf30d27726020bd0e59

Tx prefix hash: 9d03dd820d9be06e1389b1dcbcb12d84b5cef0948278835dd1c653c08c65b94e
Tx public key: 6f1d06dbd20e8269678b88573035bd40679723ac2cdd1bef6593ebfbf6e6d51c
Timestamp: 1735025666 Timestamp [UCT]: 2024-12-24 07:34:26 Age [y:d:h:m:s]: 00:097:12:06:28
Block: 1182013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69465 RingCT/type: yes/0
Extra: 016f1d06dbd20e8269678b88573035bd40679723ac2cdd1bef6593ebfbf6e6d51c021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cebd9149fb4b520a75516a0c1ee5b1420c97d4e0a3b5910736adfd3386f4ce3b 0.600000000000 1668442 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": 1182023, "vin": [ { "gen": { "height": 1182013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cebd9149fb4b520a75516a0c1ee5b1420c97d4e0a3b5910736adfd3386f4ce3b" } } ], "extra": [ 1, 111, 29, 6, 219, 210, 14, 130, 105, 103, 139, 136, 87, 48, 53, 189, 64, 103, 151, 35, 172, 44, 221, 27, 239, 101, 147, 235, 251, 246, 230, 213, 28, 2, 17, 0, 0, 0, 1, 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