Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24be32de165825f445af386637f9eed7c123f021d10cc35a78bd6b9d6cbbf3a7

Tx prefix hash: 91e6a3a320a8f44b73eafdb16ef63a08bb02ff5f504021024aa019369650e94f
Tx public key: 572e7a9e7f6c3cc6daaeafd4e460b85467b20ce708e8536f9f24ed0d96fa5cff
Timestamp: 1729695220 Timestamp [UCT]: 2024-10-23 14:53:40 Age [y:d:h:m:s]: 00:140:20:45:17
Block: 1137901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100482 RingCT/type: yes/0
Extra: 01572e7a9e7f6c3cc6daaeafd4e460b85467b20ce708e8536f9f24ed0d96fa5cff021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a24f75ed37d940e2ef5f5b779483d7490c22164288645b442bd1fa7ffd50b5a 0.600000000000 1621484 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": 1137911, "vin": [ { "gen": { "height": 1137901 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a24f75ed37d940e2ef5f5b779483d7490c22164288645b442bd1fa7ffd50b5a" } } ], "extra": [ 1, 87, 46, 122, 158, 127, 108, 60, 198, 218, 174, 175, 212, 228, 96, 184, 84, 103, 178, 12, 231, 8, 232, 83, 111, 159, 36, 237, 13, 150, 250, 92, 255, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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