Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d89e3ab690d330a6588c5feb43b42e056731f980dbbc6dc5e49625ef8cf69a77

Tx prefix hash: 18a89aa03588c3426365f7945f3fb9e3fb4f9f50e129c3ecf55713792434de66
Tx public key: 634094d570e1cdc4af1b7e53c7ea2bfd3623f720aba342f1d221cbadabc1aa52
Timestamp: 1746742182 Timestamp [UCT]: 2025-05-08 22:09:42 Age [y:d:h:m:s]: 00:185:23:24:40
Block: 1278720 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130631 RingCT/type: yes/0
Extra: 01634094d570e1cdc4af1b7e53c7ea2bfd3623f720aba342f1d221cbadabc1aa52021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d38999b799830f8f8c2f75e80f36669938cc1b77abe2382bcf8a350c49acae6 0.600000000000 1766091 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": 1278730, "vin": [ { "gen": { "height": 1278720 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d38999b799830f8f8c2f75e80f36669938cc1b77abe2382bcf8a350c49acae6" } } ], "extra": [ 1, 99, 64, 148, 213, 112, 225, 205, 196, 175, 27, 126, 83, 199, 234, 43, 253, 54, 35, 247, 32, 171, 163, 66, 241, 210, 33, 203, 173, 171, 193, 170, 82, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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