Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34745900199ace275547e74bc810c67d1dc72064fb9914a05cc7e46197f7fa74

Tx prefix hash: 03c84c4907aea610b11197e707c39c0945d3c02ea5574ec2524741d162322b61
Tx public key: a587c4d21e96d4e3fd99090915d4e831fee1eda2cb1abea0d4d18af8908ed9de
Timestamp: 1711141917 Timestamp [UCT]: 2024-03-22 21:11:57 Age [y:d:h:m:s]: 00:360:07:58:41
Block: 984140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257619 RingCT/type: yes/0
Extra: 01a587c4d21e96d4e3fd99090915d4e831fee1eda2cb1abea0d4d18af8908ed9de0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8285c3ac8136b1f8e2a84651e99ee00d9c38ea9787f73058c0c99de73b82eb34 0.600000000000 1444299 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": 984150, "vin": [ { "gen": { "height": 984140 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8285c3ac8136b1f8e2a84651e99ee00d9c38ea9787f73058c0c99de73b82eb34" } } ], "extra": [ 1, 165, 135, 196, 210, 30, 150, 212, 227, 253, 153, 9, 9, 21, 212, 232, 49, 254, 225, 237, 162, 203, 26, 190, 160, 212, 209, 138, 248, 144, 142, 217, 222, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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