Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae2a3e6e143b86df1df0bab9364b01e4f0ec921e497f75ff9a323cc958500b23

Tx prefix hash: f3f51d81c2272cc8f62880994d7f8b32dbef1260f24c165913540d653f8defba
Tx public key: bc21eba4b9d939d0a8a4287416089650d23b7f5d0be94ad3f756f91e880da6cf
Timestamp: 1715509979 Timestamp [UCT]: 2024-05-12 10:32:59 Age [y:d:h:m:s]: 00:329:02:35:00
Block: 1020364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235201 RingCT/type: yes/0
Extra: 01bc21eba4b9d939d0a8a4287416089650d23b7f5d0be94ad3f756f91e880da6cf02110000000141ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90a84a5029ac6ba1bb9d4508289849c38a981dab99437fd644937d591bbafb09 0.600000000000 1484429 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": 1020374, "vin": [ { "gen": { "height": 1020364 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90a84a5029ac6ba1bb9d4508289849c38a981dab99437fd644937d591bbafb09" } } ], "extra": [ 1, 188, 33, 235, 164, 185, 217, 57, 208, 168, 164, 40, 116, 22, 8, 150, 80, 210, 59, 127, 93, 11, 233, 74, 211, 247, 86, 249, 30, 136, 13, 166, 207, 2, 17, 0, 0, 0, 1, 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