Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82462bd030698a92079d9cb06af679868d0aeccb6610d4f55c716292d2ca183c

Tx prefix hash: 3f6b4d71052fbcd5f92d4b796daf9d3514af4b1f42e59291fcf66e24d563962c
Tx public key: f6c8c6fa82dd275b7863f5358c34416d2394aab77838fd95d50aaf57704759f5
Timestamp: 1682525922 Timestamp [UCT]: 2023-04-26 16:18:42 Age [y:d:h:m:s]: 01:349:09:46:38
Block: 747123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 510981 RingCT/type: yes/0
Extra: 01f6c8c6fa82dd275b7863f5358c34416d2394aab77838fd95d50aaf57704759f50211000000037e406890000000000000000000

1 output(s) for total of 2.053390568000 dcy

stealth address amount amount idx
00: 8dc7d744d2a38bdd8fdcc29f258d7121677a51e61b2ecf1761ef0d52bf3ac19a 2.053390568000 1194762 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": 747133, "vin": [ { "gen": { "height": 747123 } } ], "vout": [ { "amount": 2053390568, "target": { "key": "8dc7d744d2a38bdd8fdcc29f258d7121677a51e61b2ecf1761ef0d52bf3ac19a" } } ], "extra": [ 1, 246, 200, 198, 250, 130, 221, 39, 91, 120, 99, 245, 53, 140, 52, 65, 109, 35, 148, 170, 183, 120, 56, 253, 149, 213, 10, 175, 87, 112, 71, 89, 245, 2, 17, 0, 0, 0, 3, 126, 64, 104, 144, 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