Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e271c35f676dbd183ac6fee642f7e911aef66bb03e864b6623ce700280dc172c

Tx prefix hash: 635164b02c047f8b8384b4b2a9e774211f23fbd7594cbca0109ba90ea350b522
Tx public key: a8cf3db71e197f2db4ec13c8c11267d88fb00c9db2bb632d7ad8f02dcce1183c
Timestamp: 1720641876 Timestamp [UCT]: 2024-07-10 20:04:36 Age [y:d:h:m:s]: 01:123:18:58:48
Block: 1062880 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346990 RingCT/type: yes/0
Extra: 01a8cf3db71e197f2db4ec13c8c11267d88fb00c9db2bb632d7ad8f02dcce1183c02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7429548a51a26131ec510242077c42c4f9fa42dd6e8fb78c080c1fe231bc74af 0.600000000000 1533391 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": 1062890, "vin": [ { "gen": { "height": 1062880 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7429548a51a26131ec510242077c42c4f9fa42dd6e8fb78c080c1fe231bc74af" } } ], "extra": [ 1, 168, 207, 61, 183, 30, 25, 127, 45, 180, 236, 19, 200, 193, 18, 103, 216, 143, 176, 12, 157, 178, 187, 99, 45, 122, 216, 240, 45, 204, 225, 24, 60, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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