Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79a57dd16ceafdcd2629d0d574a30ff34a1772d0019fc9d92940a7bdc6314aec

Tx prefix hash: 2f18442106124c389718ee35bde59b025df3d623abf2bed9047e2d6b7b670151
Tx public key: 6a0c2e0d4b43ae134b916ab96262eee25ebb5fbaac1ea6ec984246741491a539
Timestamp: 1699877400 Timestamp [UCT]: 2023-11-13 12:10:00 Age [y:d:h:m:s]: 01:362:07:29:20
Block: 890732 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 517851 RingCT/type: yes/0
Extra: 016a0c2e0d4b43ae134b916ab96262eee25ebb5fbaac1ea6ec984246741491a53902110000000d75e3f0e9000000000000000000

1 output(s) for total of 0.686491431000 dcy

stealth address amount amount idx
00: 17b44b98a4f3a3fc360584ecd88e7eb45eb9d8895de81d9f12c202d2840972ca 0.686491431000 1346763 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": 890742, "vin": [ { "gen": { "height": 890732 } } ], "vout": [ { "amount": 686491431, "target": { "key": "17b44b98a4f3a3fc360584ecd88e7eb45eb9d8895de81d9f12c202d2840972ca" } } ], "extra": [ 1, 106, 12, 46, 13, 75, 67, 174, 19, 75, 145, 106, 185, 98, 98, 238, 226, 94, 187, 95, 186, 172, 30, 166, 236, 152, 66, 70, 116, 20, 145, 165, 57, 2, 17, 0, 0, 0, 13, 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