Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5646b6c0cc21d8a13eb5fac3004bcdf4c31c16520019347f8b481ae33755d35d

Tx prefix hash: 11b82798d33d574a0e818c96d044cf1c08d0bfe5233b8357717927962dd97d47
Tx public key: 5fdd6b21a8c7fb206647316ea2a8479a1b45cb0e680dc053172aac71549e8591
Timestamp: 1714987497 Timestamp [UCT]: 2024-05-06 09:24:57 Age [y:d:h:m:s]: 00:338:11:08:28
Block: 1016003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241932 RingCT/type: yes/0
Extra: 015fdd6b21a8c7fb206647316ea2a8479a1b45cb0e680dc053172aac71549e85910211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13e9c2cb74c092ca36ab17184e2cfa4e263b88d69db3869788c3d1c444295507 0.600000000000 1479462 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": 1016013, "vin": [ { "gen": { "height": 1016003 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13e9c2cb74c092ca36ab17184e2cfa4e263b88d69db3869788c3d1c444295507" } } ], "extra": [ 1, 95, 221, 107, 33, 168, 199, 251, 32, 102, 71, 49, 110, 162, 168, 71, 154, 27, 69, 203, 14, 104, 13, 192, 83, 23, 42, 172, 113, 84, 158, 133, 145, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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