Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de96047fc0231bdc8abf491fbea74cf5d21dee3322f46cec611042a4c55d603a

Tx prefix hash: b1c316a2bc66d4b5cc20003dc696df4e74dfa9ffb618def6b7b334e39af83b64
Tx public key: ffe6931b906b55304c62a74221c5d9d86920951f62dbf5e3e46c0ef7f1e709e5
Timestamp: 1723310849 Timestamp [UTC]: 2024-08-10 17:27:29 Age [y:d:h:m:s]: 02:096:01:34:39
Block: 1085004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 593341 RingCT/type: yes/0
Extra: 01ffe6931b906b55304c62a74221c5d9d86920951f62dbf5e3e46c0ef7f1e709e5021100000006e914dd15000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c3dca07ad482f4c5ced6cb5958bf5294687b5db0941a6da2ca71274992537458 0.000600000000 1559481 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 dinastycoin-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": 1085014, "vin": [ { "gen": { "height": 1085004 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3dca07ad482f4c5ced6cb5958bf5294687b5db0941a6da2ca71274992537458" } } ], "extra": [ 1, 255, 230, 147, 27, 144, 107, 85, 48, 76, 98, 167, 66, 33, 197, 217, 216, 105, 32, 149, 31, 98, 219, 245, 227, 228, 108, 14, 247, 241, 231, 9, 229, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: