Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b119b285d75fdb4626b96a4c518db956f8106bd2ea8d0f36d9fb7f2e01a993ba

Tx prefix hash: aed925acffd2dec77a8e754e0fe30210091c3848f2585ed4dc19faa301683ed0
Tx public key: b7b92810f7ad6a87e156cc8652959f3404b2b9a41ce6e49fb565e6fba5058368
Timestamp: 1715499408 Timestamp [UCT]: 2024-05-12 07:36:48 Age [y:d:h:m:s]: 00:243:04:54:52
Block: 1020272 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174036 RingCT/type: yes/0
Extra: 01b7b92810f7ad6a87e156cc8652959f3404b2b9a41ce6e49fb565e6fba505836802110000000241ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c25518d80c39087a33a7145cc14d5bcf47b2422606de837988c6073fdf9d2c0 0.600000000000 1484333 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": 1020282, "vin": [ { "gen": { "height": 1020272 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c25518d80c39087a33a7145cc14d5bcf47b2422606de837988c6073fdf9d2c0" } } ], "extra": [ 1, 183, 185, 40, 16, 247, 173, 106, 135, 225, 86, 204, 134, 82, 149, 159, 52, 4, 178, 185, 164, 28, 230, 228, 159, 181, 101, 230, 251, 165, 5, 131, 104, 2, 17, 0, 0, 0, 2, 65, 238, 28, 155, 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