Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa04901fdae10eacc9573ade8e98b7b53ec2b2d309faf070ec644943d6159a82

Tx prefix hash: 69fb643d83edd77626cff3a35d4167b53ef362dabffab6685c8383e18df3a803
Tx public key: 731e89159b50a54b07b50bb0c90554a5d2cf60dc7732c3abe51a1e7da1b66ea7
Timestamp: 1720494167 Timestamp [UCT]: 2024-07-09 03:02:47 Age [y:d:h:m:s]: 01:122:22:38:45
Block: 1061659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346380 RingCT/type: yes/0
Extra: 01731e89159b50a54b07b50bb0c90554a5d2cf60dc7732c3abe51a1e7da1b66ea702110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c713c44c2399fc20cfaef313c0db99e339cf7f6a144c75bc99a5766b4944d6c3 0.600000000000 1532152 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": 1061669, "vin": [ { "gen": { "height": 1061659 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c713c44c2399fc20cfaef313c0db99e339cf7f6a144c75bc99a5766b4944d6c3" } } ], "extra": [ 1, 115, 30, 137, 21, 155, 80, 165, 75, 7, 181, 11, 176, 201, 5, 84, 165, 210, 207, 96, 220, 119, 50, 195, 171, 229, 26, 30, 125, 161, 182, 110, 167, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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