Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b7223ae0c88e2ca6148371bb3241d41d6b4686df3a67eb9d984c4e28114550d

Tx prefix hash: 9be44e59e206424e7de6d21d8501513625660c6a1f663042e1da631331d1cdda
Tx public key: 86eda65beab87eed6392ff13d5bf4c86a6b7ca332650d9cff2d81ec0d577a0b3
Timestamp: 1699571265 Timestamp [UCT]: 2023-11-09 23:07:45 Age [y:d:h:m:s]: 01:077:01:18:28
Block: 888196 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316446 RingCT/type: yes/0
Extra: 0186eda65beab87eed6392ff13d5bf4c86a6b7ca332650d9cff2d81ec0d577a0b302110000000475e3f0e9000000000000000000

1 output(s) for total of 0.699903145000 dcy

stealth address amount amount idx
00: 8e1a6092982da758c446a42a83b1f272b8a79af3ccec71ae597d26673ae4507d 0.699903145000 1344127 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": 888206, "vin": [ { "gen": { "height": 888196 } } ], "vout": [ { "amount": 699903145, "target": { "key": "8e1a6092982da758c446a42a83b1f272b8a79af3ccec71ae597d26673ae4507d" } } ], "extra": [ 1, 134, 237, 166, 91, 234, 184, 126, 237, 99, 146, 255, 19, 213, 191, 76, 134, 166, 183, 202, 51, 38, 80, 217, 207, 242, 216, 30, 192, 213, 119, 160, 179, 2, 17, 0, 0, 0, 4, 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