Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1ad7a1543ea6f3e9a8c862c1ee27875d408b2189bafc3abef0b6650dc12f16e

Tx prefix hash: 091c7c1ea08bc3931ffce5a843d0d89f01f1427e68e834c3ca5845335ce608d9
Tx public key: c453016c02a1b5df89d08cb0109fba9b078927b9e722311f60581c979346aa76
Timestamp: 1703796110 Timestamp [UCT]: 2023-12-28 20:41:50 Age [y:d:h:m:s]: 01:106:14:09:30
Block: 923217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337300 RingCT/type: yes/0
Extra: 01c453016c02a1b5df89d08cb0109fba9b078927b9e722311f60581c979346aa76021100000003ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36ef4a434bb67604256fa62c2bb592e52dbfd81a2681511ae5ddd7ae170e2973 0.600000000000 1380943 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": 923227, "vin": [ { "gen": { "height": 923217 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36ef4a434bb67604256fa62c2bb592e52dbfd81a2681511ae5ddd7ae170e2973" } } ], "extra": [ 1, 196, 83, 1, 108, 2, 161, 181, 223, 137, 208, 140, 176, 16, 159, 186, 155, 7, 137, 39, 185, 231, 34, 49, 31, 96, 88, 28, 151, 147, 70, 170, 118, 2, 17, 0, 0, 0, 3, 173, 86, 148, 172, 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