Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dab9c0c010aa404cdf06d5324307ebe65c800f3b5c9158849fd14d8d57bf9dbe

Tx prefix hash: 099f916dd5b60b3d6e00ebe0291c0b6df81b7d196da123f9f81e803f08f5e93b
Tx public key: 1e7a9765b0ddfa436a6c7840bf7fd2805ff8239d598ae3952d04701441ab0600
Timestamp: 1682351754 Timestamp [UCT]: 2023-04-24 15:55:54 Age [y:d:h:m:s]: 01:223:07:29:21
Block: 745680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 421061 RingCT/type: yes/0
Extra: 011e7a9765b0ddfa436a6c7840bf7fd2805ff8239d598ae3952d04701441ab0600021100000003e7ace25d000000000000000000

1 output(s) for total of 2.076121773000 dcy

stealth address amount amount idx
00: 50146bf0d8de04fa18bc99aed7c66b16a7e851d332280862d567530b3d017b1c 2.076121773000 1193151 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": 745690, "vin": [ { "gen": { "height": 745680 } } ], "vout": [ { "amount": 2076121773, "target": { "key": "50146bf0d8de04fa18bc99aed7c66b16a7e851d332280862d567530b3d017b1c" } } ], "extra": [ 1, 30, 122, 151, 101, 176, 221, 250, 67, 106, 108, 120, 64, 191, 127, 210, 128, 95, 248, 35, 157, 89, 138, 227, 149, 45, 4, 112, 20, 65, 171, 6, 0, 2, 17, 0, 0, 0, 3, 231, 172, 226, 93, 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