Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e220d308e88e234dd064c9942ce3816ede97560c0cbf6b20ba6453847054b15

Tx prefix hash: 5613c682137a355d30c77f742f37f4c29e903e390813a8371b3870c43088c882
Tx public key: e5d16e3dab16db0e5409ec94cdb78fb0a0682d522f52127e9c859f85ddb0e6cd
Timestamp: 1711948529 Timestamp [UCT]: 2024-04-01 05:15:29 Age [y:d:h:m:s]: 01:221:04:47:34
Block: 990771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416808 RingCT/type: yes/0
Extra: 01e5d16e3dab16db0e5409ec94cdb78fb0a0682d522f52127e9c859f85ddb0e6cd0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0bf6bcb6e06d018dd8e16131875023fdcb7b3b89f7c5ca6f1e3629595cabf233 0.600000000000 1451099 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": 990781, "vin": [ { "gen": { "height": 990771 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0bf6bcb6e06d018dd8e16131875023fdcb7b3b89f7c5ca6f1e3629595cabf233" } } ], "extra": [ 1, 229, 209, 110, 61, 171, 22, 219, 14, 84, 9, 236, 148, 205, 183, 143, 176, 160, 104, 45, 82, 47, 82, 18, 126, 156, 133, 159, 133, 221, 176, 230, 205, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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