Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 086c98e5b719a9782f4c58856d082cde93bd2a6726ba0006b4d2e3c0c9f79509

Tx prefix hash: f493b1bd0a63a418b0c10c317f16e539be4617be114c7dd05fce4e362ad2c87e
Tx public key: 46cf3d4741e49fabb73d55779eb712170db0ca1892db691ec96959f3c296ab48
Timestamp: 1699345405 Timestamp [UCT]: 2023-11-07 08:23:25 Age [y:d:h:m:s]: 01:189:16:33:32
Block: 886321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396794 RingCT/type: yes/0
Extra: 0146cf3d4741e49fabb73d55779eb712170db0ca1892db691ec96959f3c296ab48021100000001faf35c9c000000000000000000

1 output(s) for total of 0.709987334000 dcy

stealth address amount amount idx
00: 222d90812e3bffc2c3c6815678dc65b5ceb6e3031ac5e9ea85f9624024e71fe6 0.709987334000 1342136 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": 886331, "vin": [ { "gen": { "height": 886321 } } ], "vout": [ { "amount": 709987334, "target": { "key": "222d90812e3bffc2c3c6815678dc65b5ceb6e3031ac5e9ea85f9624024e71fe6" } } ], "extra": [ 1, 70, 207, 61, 71, 65, 228, 159, 171, 183, 61, 85, 119, 158, 183, 18, 23, 13, 176, 202, 24, 146, 219, 105, 30, 201, 105, 89, 243, 194, 150, 171, 72, 2, 17, 0, 0, 0, 1, 250, 243, 92, 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