Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c26682a2398f5aad4f29329cffb41a1fc025feedc0b87f6633910bca58610b0e

Tx prefix hash: 17b27b3c5c3d3debf28ba2ffcd8d514b7074870843dae7195a38cfb1a0db58ae
Tx public key: 0d515ce3be257cd273d2d6f43668eb10f67c1ba2ac48b97e5fa0cbf864da07ec
Timestamp: 1741052617 Timestamp [UCT]: 2025-03-04 01:43:37 Age [y:d:h:m:s]: 00:096:01:18:57
Block: 1231623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68718 RingCT/type: yes/0
Extra: 010d515ce3be257cd273d2d6f43668eb10f67c1ba2ac48b97e5fa0cbf864da07ec0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600160000000 dcy

stealth address amount amount idx
00: 9c6f542bcccc23aab0f7945b1ed11edc08b555b7621f6fa041d955b547fd4247 0.600160000000 1718532 of 0

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": 1231633, "vin": [ { "gen": { "height": 1231623 } } ], "vout": [ { "amount": 600160000, "target": { "key": "9c6f542bcccc23aab0f7945b1ed11edc08b555b7621f6fa041d955b547fd4247" } } ], "extra": [ 1, 13, 81, 92, 227, 190, 37, 124, 210, 115, 210, 214, 244, 54, 104, 235, 16, 246, 124, 27, 162, 172, 72, 185, 126, 95, 160, 203, 248, 100, 218, 7, 236, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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