Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 564790aa29b52185897ff341b993cc833d83eff505e51a4f0411f774f903a7dc

Tx prefix hash: 422093f4767ccf956518e95580fd355cc508df8bb2ec1d4d4806775f193c82a0
Tx public key: e99ea3992261ef2a6d54e14b0a3dc616e5e8a319e27b72cf402f70f4a2e499f9
Timestamp: 1732884821 Timestamp [UCT]: 2024-11-29 12:53:41 Age [y:d:h:m:s]: 00:115:11:44:26
Block: 1164284 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82323 RingCT/type: yes/0
Extra: 01e99ea3992261ef2a6d54e14b0a3dc616e5e8a319e27b72cf402f70f4a2e499f90211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c97b321057e69652495833ff75c4f7beba67b56614c1717b3550b82d388e72e0 0.600000000000 1649957 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": 1164294, "vin": [ { "gen": { "height": 1164284 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c97b321057e69652495833ff75c4f7beba67b56614c1717b3550b82d388e72e0" } } ], "extra": [ 1, 233, 158, 163, 153, 34, 97, 239, 42, 109, 84, 225, 75, 10, 61, 198, 22, 229, 232, 163, 25, 226, 123, 114, 207, 64, 47, 112, 244, 162, 228, 153, 249, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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