Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 373a7bed68db4fd9e8970c81d1645d5d874c2a8b7def4032adb90f6b2d65e1bb

Tx prefix hash: 6c58d1fa1b87cf7f0c55610ee4a4594c6902ddd18a92ae026414e9b00f305f12
Tx public key: 22911bd3ec78e23ab780b49497d46507f2be178c93f0e11551fdd5be80ed081f
Timestamp: 1733265287 Timestamp [UCT]: 2024-12-03 22:34:47 Age [y:d:h:m:s]: 00:115:12:29:51
Block: 1167433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82362 RingCT/type: yes/0
Extra: 0122911bd3ec78e23ab780b49497d46507f2be178c93f0e11551fdd5be80ed081f0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a4e19f546fa64f13a258e034e2ea3e65286a42c36ce75c8e97499e2fac22a84 0.600000000000 1653128 of 15

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": 1167443, "vin": [ { "gen": { "height": 1167433 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a4e19f546fa64f13a258e034e2ea3e65286a42c36ce75c8e97499e2fac22a84" } } ], "extra": [ 1, 34, 145, 27, 211, 236, 120, 226, 58, 183, 128, 180, 148, 151, 212, 101, 7, 242, 190, 23, 140, 147, 240, 225, 21, 81, 253, 213, 190, 128, 237, 8, 31, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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