Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2348db794f71d187cc0a66e7e9d2e2d84cdc149a444d5c0e31931e2717842cf

Tx prefix hash: 5012165963e3b8c8645aed0e666e3c2f273905953aca4777d9dce5745e84f25a
Tx public key: 36b489d98fd85154865b925d97360728bd947e98b72ad0b35235324642ab9ff0
Timestamp: 1775058043 Timestamp [UTC]: 2026-04-01 15:40:43 Age [y:d:h:m:s]: 00:232:04:55:53
Block: 1510600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171543 RingCT/type: yes/0
Extra: 0136b489d98fd85154865b925d97360728bd947e98b72ad0b35235324642ab9ff0021100000009e3d7dc9f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 124e4cbdde3b7c57b95a411d25d0f33e4ca6b310c6fe35b87c2182dc81a49c86 0.000600000000 2000386 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": 1510610, "vin": [ { "gen": { "height": 1510600 } } ], "vout": [ { "amount": 600000000, "target": { "key": "124e4cbdde3b7c57b95a411d25d0f33e4ca6b310c6fe35b87c2182dc81a49c86" } } ], "extra": [ 1, 54, 180, 137, 217, 143, 216, 81, 84, 134, 91, 146, 93, 151, 54, 7, 40, 189, 148, 126, 152, 183, 42, 208, 179, 82, 53, 50, 70, 66, 171, 159, 240, 2, 17, 0, 0, 0, 9, 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: