Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e89e516f4b71b19f86ddb69dd1b1d97a3ad28e949762e2f80345df880cf8093e

Tx prefix hash: 015d381d12dbd03a777310a1398a0b68816b1f337a5765cb75c4af9e3529690d
Tx public key: 2bb9506eae1c332787a308e1a2a069a5fa9d7400d6829d9e09ccacbb90361cd3
Timestamp: 1727932850 Timestamp [UCT]: 2024-10-03 05:20:50 Age [y:d:h:m:s]: 00:113:02:19:11
Block: 1123323 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80816 RingCT/type: yes/0
Extra: 012bb9506eae1c332787a308e1a2a069a5fa9d7400d6829d9e09ccacbb90361cd3021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f671faed0c26760d25e2b8f8720e821795fff9b25020aede397a068999f51b16 0.600000000000 1605856 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": 1123333, "vin": [ { "gen": { "height": 1123323 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f671faed0c26760d25e2b8f8720e821795fff9b25020aede397a068999f51b16" } } ], "extra": [ 1, 43, 185, 80, 110, 174, 28, 51, 39, 135, 163, 8, 225, 162, 160, 105, 165, 250, 157, 116, 0, 214, 130, 157, 158, 9, 204, 172, 187, 144, 54, 28, 211, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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