Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f0549e9fef6b53cfd03cd77bdd7f4dfe1e475e08cc09b5d55d0ca394c7db3de

Tx prefix hash: c14bd0849f9dc0ded85790b5c4657cb73c60084940fdf6d2690ed96d8e768a34
Tx public key: d8b1f4ba2ceb1bb6f82dbebe740cba5665e6f08d8d35b98fcf5a18972d3125ac
Timestamp: 1638030626 Timestamp [UCT]: 2021-11-27 16:30:26 Age [y:d:h:m:s]: 03:107:19:56:04
Block: 383361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 855768 RingCT/type: yes/0
Extra: 01d8b1f4ba2ceb1bb6f82dbebe740cba5665e6f08d8d35b98fcf5a18972d3125ac02110000000ce9564d6f000000000000000000

1 output(s) for total of 32.945104831000 dcy

stealth address amount amount idx
00: 5ab1b9e2048e1cac235c639c7aaae5a73cc8829915e8c108a22e8e095e6d668f 32.945104831000 773998 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": 383371, "vin": [ { "gen": { "height": 383361 } } ], "vout": [ { "amount": 32945104831, "target": { "key": "5ab1b9e2048e1cac235c639c7aaae5a73cc8829915e8c108a22e8e095e6d668f" } } ], "extra": [ 1, 216, 177, 244, 186, 44, 235, 27, 182, 248, 45, 190, 190, 116, 12, 186, 86, 101, 230, 240, 141, 141, 53, 185, 143, 207, 90, 24, 151, 45, 49, 37, 172, 2, 17, 0, 0, 0, 12, 233, 86, 77, 111, 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