Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56d18ed2f4739dc091103cc4db7bbb40cede9bd4b328cf2e92b2e743ecce781c

Tx prefix hash: 8e8968220c282c9918f1e52e72604184d3a4b7eef4fb734e082b0e475cb68fd0
Tx public key: feea6355318de1228379ad23a5ab424115ec4fe88f0a7bea822b50d17f6ae33d
Timestamp: 1702585207 Timestamp [UCT]: 2023-12-14 20:20:07 Age [y:d:h:m:s]: 01:330:07:33:00
Block: 913170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 494936 RingCT/type: yes/0
Extra: 01feea6355318de1228379ad23a5ab424115ec4fe88f0a7bea822b50d17f6ae33d02110000000575e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7985dec67687164964916b5361506451e6788617933d7493ea5f91a7915e2697 0.600000000000 1370416 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": 913180, "vin": [ { "gen": { "height": 913170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7985dec67687164964916b5361506451e6788617933d7493ea5f91a7915e2697" } } ], "extra": [ 1, 254, 234, 99, 85, 49, 141, 225, 34, 131, 121, 173, 35, 165, 171, 66, 65, 21, 236, 79, 232, 143, 10, 123, 234, 130, 43, 80, 209, 127, 106, 227, 61, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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