Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed3d8dd8c043f372b26b79d719f8cae299190cfaf684027a0f6c5c267f0ff2fb

Tx prefix hash: d4deb83d76b13849a368800ed73a8b584a1f8cce50057b527270d1adb15d00b3
Tx public key: eb8dbd0a2639244e2bd00652ac4595e5c725597b5e0a64ae89a633f8a4a9f103
Timestamp: 1707158590 Timestamp [UTC]: 2024-02-05 18:43:10 Age [y:d:h:m:s]: 02:290:20:58:12
Block: 951085 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 732409 RingCT/type: yes/0
Extra: 01eb8dbd0a2639244e2bd00652ac4595e5c725597b5e0a64ae89a633f8a4a9f10302110000000252d47e94000000000000000000

1 output(s) for total of 0.000600010000 xmr

stealth address amount amount idx tag
00: 655fef58ad6e0462d9c57e03b58436b23b170ad1d5303da1f19b4bafda7adb03 0.000600010000 1409801 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 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": 951095, "vin": [ { "gen": { "height": 951085 } } ], "vout": [ { "amount": 600010000, "target": { "key": "655fef58ad6e0462d9c57e03b58436b23b170ad1d5303da1f19b4bafda7adb03" } } ], "extra": [ 1, 235, 141, 189, 10, 38, 57, 36, 78, 43, 208, 6, 82, 172, 69, 149, 229, 199, 37, 89, 123, 94, 10, 100, 174, 137, 166, 51, 248, 164, 169, 241, 3, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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: