Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab584a4e0ca92d9c7228816547bd7acf38037e07a379a6acd9d0f5ec786d2f64

Tx prefix hash: 142ccab88daf068b424cff5231ff8210b983132580f4dafda3a62fb7e9eef2df
Tx public key: bea14f7f895eeef27fc6f2106d32f0db33540477e402d2362050df04c2c73497
Timestamp: 1673565215 Timestamp [UCT]: 2023-01-12 23:13:35 Age [y:d:h:m:s]: 02:006:00:12:50
Block: 673462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 526179 RingCT/type: yes/0
Extra: 01bea14f7f895eeef27fc6f2106d32f0db33540477e402d2362050df04c2c7349702110000000175e3f0e9000000000000000000

1 output(s) for total of 3.601975701000 dcy

stealth address amount amount idx
00: b223402165befa7c5e37089bbcc5bf9a33aadd34c9b04238064d396cfd6e26d2 3.601975701000 1115071 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": 673472, "vin": [ { "gen": { "height": 673462 } } ], "vout": [ { "amount": 3601975701, "target": { "key": "b223402165befa7c5e37089bbcc5bf9a33aadd34c9b04238064d396cfd6e26d2" } } ], "extra": [ 1, 190, 161, 79, 127, 137, 94, 238, 242, 127, 198, 242, 16, 109, 50, 240, 219, 51, 84, 4, 119, 228, 2, 210, 54, 32, 80, 223, 4, 194, 199, 52, 151, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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