Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e18aeba2cdb60a0de2b8590c1f78c3e81a18a063175abd716c6d8dde9ebf06d3

Tx prefix hash: 9030585f938aa148119bf13b46f1ce72c265a7a413e2d9e8dd3f7c2827be45f3
Tx public key: d6015931be10d3ab5cfb19feb6d3cda6330d214f8ab948d394e388cb22248b9e
Timestamp: 1694888881 Timestamp [UCT]: 2023-09-16 18:28:01 Age [y:d:h:m:s]: 01:215:11:05:16
Block: 849560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 415080 RingCT/type: yes/0
Extra: 01d6015931be10d3ab5cfb19feb6d3cda6330d214f8ab948d394e388cb22248b9e02110000000a75e3f0e9000000000000000000

1 output(s) for total of 0.939842561000 dcy

stealth address amount amount idx
00: 68bb0d6dcea252aea38fede5e66755f25c88f01a343e99ce6fa4368d9589a918 0.939842561000 1303230 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": 849570, "vin": [ { "gen": { "height": 849560 } } ], "vout": [ { "amount": 939842561, "target": { "key": "68bb0d6dcea252aea38fede5e66755f25c88f01a343e99ce6fa4368d9589a918" } } ], "extra": [ 1, 214, 1, 89, 49, 190, 16, 211, 171, 92, 251, 25, 254, 182, 211, 205, 166, 51, 13, 33, 79, 138, 185, 72, 211, 148, 227, 136, 203, 34, 36, 139, 158, 2, 17, 0, 0, 0, 10, 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