Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00231d3936099441f6ffa67d445b0d38ac6a5cf3eb0efd08bc308a4b7ce57c99

Tx prefix hash: b26e658435cbfe3d0d9e33cb2a03d954522e4f8c4ed97752abf0205f5437a5b3
Tx public key: 8b9944533ab556cc781f52dc20897aa37bf52db8d716958ddec90e2a5f55e3b2
Timestamp: 1772817150 Timestamp [UTC]: 2026-03-06 17:12:30 Age [y:d:h:m:s]: 00:260:09:06:47
Block: 1492070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191424 RingCT/type: yes/0
Extra: 018b9944533ab556cc781f52dc20897aa37bf52db8d716958ddec90e2a5f55e3b2021100000008f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a1b9a15204ce874926f246d940d32d9743c9f49dae4363ad2055e5e36bb7e570 0.000600000000 1981608 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": 1492080, "vin": [ { "gen": { "height": 1492070 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1b9a15204ce874926f246d940d32d9743c9f49dae4363ad2055e5e36bb7e570" } } ], "extra": [ 1, 139, 153, 68, 83, 58, 181, 86, 204, 120, 31, 82, 220, 32, 137, 122, 163, 123, 245, 45, 184, 215, 22, 149, 141, 222, 201, 14, 42, 95, 85, 227, 178, 2, 17, 0, 0, 0, 8, 241, 136, 200, 168, 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: