Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01706286b3cf60bfa4db08cce26e40a41ad8a15fb6b60a1a22310ba5ab13963f

Tx prefix hash: 0650ce43bf468d43c33cf39490fc1fe057c9b770760af9fb578e4be32bb1ae0a
Tx public key: 8b8ad4a4971a0532c3b5ad5ab505eabf736b8ad8bedd4bf6516cd3d42d34967f
Timestamp: 1699145065 Timestamp [UCT]: 2023-11-05 00:44:25 Age [y:d:h:m:s]: 02:065:06:37:57
Block: 884912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 566267 RingCT/type: yes/0
Extra: 018b8ad4a4971a0532c3b5ad5ab505eabf736b8ad8bedd4bf6516cd3d42d34967f02110000000533af99f4000000000000000000

1 output(s) for total of 0.717660767000 dcy

stealth address amount amount idx
00: b09bdfded27a1e98ae6b52ab9340ae4cd6dd25c0312178efbde270208ad6fec9 0.717660767000 1340661 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": 884922, "vin": [ { "gen": { "height": 884912 } } ], "vout": [ { "amount": 717660767, "target": { "key": "b09bdfded27a1e98ae6b52ab9340ae4cd6dd25c0312178efbde270208ad6fec9" } } ], "extra": [ 1, 139, 138, 212, 164, 151, 26, 5, 50, 195, 181, 173, 90, 181, 5, 234, 191, 115, 107, 138, 216, 190, 221, 75, 246, 81, 108, 211, 212, 45, 52, 150, 127, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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