Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 525f80201165bcda98cfc00e1f0fac0a482b49cbcf37101af3f439f71f20aed3

Tx prefix hash: d3d3e1da1f530d3488667a985210b1693efb7c2a5b8fdec77d082127b5f46172
Tx public key: c7ecdd80f7c9760d28247ec343beb68440794d2598107ccd09fc056ea8de7e0b
Timestamp: 1715473143 Timestamp [UCT]: 2024-05-12 00:19:03 Age [y:d:h:m:s]: 01:019:12:06:23
Block: 1020055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274857 RingCT/type: yes/0
Extra: 01c7ecdd80f7c9760d28247ec343beb68440794d2598107ccd09fc056ea8de7e0b02110000000741ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d002dd54c24af6041ebae44e11ca20efc2fc11fdc2c2e6b05e0b218bb46c7c8d 0.600000000000 1484114 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": 1020065, "vin": [ { "gen": { "height": 1020055 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d002dd54c24af6041ebae44e11ca20efc2fc11fdc2c2e6b05e0b218bb46c7c8d" } } ], "extra": [ 1, 199, 236, 221, 128, 247, 201, 118, 13, 40, 36, 126, 195, 67, 190, 182, 132, 64, 121, 77, 37, 152, 16, 124, 205, 9, 252, 5, 110, 168, 222, 126, 11, 2, 17, 0, 0, 0, 7, 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