Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9500f53a49c155a91ea9f259c2b891f35df25cf32993e382c5a805450d1bbf2

Tx prefix hash: bd3a83777a4d7fcabf75902859c2b9cda2b35490026c5c4d06bae827f29cee1f
Tx public key: dcffebc83e86cc34fe5d722d1271470fd0443696a2398d99bdef704b4d7ffce2
Timestamp: 1713811264 Timestamp [UCT]: 2024-04-22 18:41:04 Age [y:d:h:m:s]: 00:349:16:08:26
Block: 1006246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249963 RingCT/type: yes/0
Extra: 01dcffebc83e86cc34fe5d722d1271470fd0443696a2398d99bdef704b4d7ffce202110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 384ae12738368add2f27e92a458d6f388c23675fe531c4aed3f82fde11f4d92d 0.600000000000 1467204 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": 1006256, "vin": [ { "gen": { "height": 1006246 } } ], "vout": [ { "amount": 600000000, "target": { "key": "384ae12738368add2f27e92a458d6f388c23675fe531c4aed3f82fde11f4d92d" } } ], "extra": [ 1, 220, 255, 235, 200, 62, 134, 204, 52, 254, 93, 114, 45, 18, 113, 71, 15, 208, 68, 54, 150, 162, 57, 141, 153, 189, 239, 112, 75, 77, 127, 252, 226, 2, 17, 0, 0, 0, 6, 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