Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2ad2b8e0eda48f5b9855e691d920d0f7dad7f8a4b925d9db28cd4ece5f64329

Tx prefix hash: da37d42b03a07925f1acb73829efa03ed8953d5e6b031584fba4065da0d8923d
Tx public key: ae8a0eb4a41bdeaddb1baac353da8fb4491e93a1946131c8d66d7ccb28564bf6
Timestamp: 1673496231 Timestamp [UCT]: 2023-01-12 04:03:51 Age [y:d:h:m:s]: 02:346:08:41:38
Block: 672867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 766995 RingCT/type: yes/0
Extra: 01ae8a0eb4a41bdeaddb1baac353da8fb4491e93a1946131c8d66d7ccb28564bf6021100000001e6d27f9c000000000000000000

1 output(s) for total of 3.618364065000 dcy

stealth address amount amount idx
00: cb4b47f5a91fd2ea4e0e2c41bb0cbc0a3bcab2b3e55ecb8ce53e366ea7218bc2 3.618364065000 1114436 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": 672877, "vin": [ { "gen": { "height": 672867 } } ], "vout": [ { "amount": 3618364065, "target": { "key": "cb4b47f5a91fd2ea4e0e2c41bb0cbc0a3bcab2b3e55ecb8ce53e366ea7218bc2" } } ], "extra": [ 1, 174, 138, 14, 180, 164, 27, 222, 173, 219, 27, 170, 195, 83, 218, 143, 180, 73, 30, 147, 161, 148, 97, 49, 200, 214, 109, 124, 203, 40, 86, 75, 246, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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