Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24b13b0b6e096e5e59a68484ef3ceccecfd91b4a7cbf4eb4632ab4b95af47734

Tx prefix hash: 95e78636330545f64cb0e7787519e1be18698d7cd57a634d4abd72902eb2bcbc
Tx public key: a9a5c8160d5f97ad90705e0c1f133db0394ce41e350e78e1e323a41300517ad4
Timestamp: 1577256523 Timestamp [UCT]: 2019-12-25 06:48:43 Age [y:d:h:m:s]: 05:009:08:33:31
Block: 31215 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1156748 RingCT/type: yes/0
Extra: 01a9a5c8160d5f97ad90705e0c1f133db0394ce41e350e78e1e323a41300517ad40211000000294fb58672000000000000000000

1 output(s) for total of 483.696124300000 dcy

stealth address amount amount idx
00: 9c2767db609fbda65cea21a03458fc5b2c3ff144ea1b69f9da1f537008c5a211 483.696124300000 51609 of 0

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": 31225, "vin": [ { "gen": { "height": 31215 } } ], "vout": [ { "amount": 483696124300, "target": { "key": "9c2767db609fbda65cea21a03458fc5b2c3ff144ea1b69f9da1f537008c5a211" } } ], "extra": [ 1, 169, 165, 200, 22, 13, 95, 151, 173, 144, 112, 94, 12, 31, 19, 61, 176, 57, 76, 228, 30, 53, 14, 120, 225, 227, 35, 164, 19, 0, 81, 122, 212, 2, 17, 0, 0, 0, 41, 79, 181, 134, 114, 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