Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3afbe199fe1af77ff63df7beb876dedcd8ee4a8b3a081031bbd30a55f8d6fd1

Tx prefix hash: 0afbfe6fdd1546cf881a72b2a0842784acd655280646bef213058a6126600513
Tx public key: 6d62768966947049fc00f1d4ffc63c8e1f639b35f65f1deb5ea0236d8742b798
Timestamp: 1774947774 Timestamp [UTC]: 2026-03-31 09:02:54 Age [y:d:h:m:s]: 00:229:13:18:39
Block: 1509693 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169505 RingCT/type: yes/0
Extra: 016d62768966947049fc00f1d4ffc63c8e1f639b35f65f1deb5ea0236d8742b798021100000002e3d7dc9f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: dd90bae2f13485cfae413d84ec6305e6db68196644589bd484de0bb7a397af1c 0.000600000000 1999469 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": 1509703, "vin": [ { "gen": { "height": 1509693 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd90bae2f13485cfae413d84ec6305e6db68196644589bd484de0bb7a397af1c" } } ], "extra": [ 1, 109, 98, 118, 137, 102, 148, 112, 73, 252, 0, 241, 212, 255, 198, 60, 142, 31, 99, 155, 53, 246, 95, 29, 235, 94, 160, 35, 109, 135, 66, 183, 152, 2, 17, 0, 0, 0, 2, 227, 215, 220, 159, 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: