Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1b566f20b1d5bcfc71ab030cf85cb6c6a33f3f8b71583579d126a0bae54f06b

Tx prefix hash: 970eff3d2aa567807e4bd40f2d6ae9d98f683a60f0270ed82178bc65eddc1f48
Tx public key: 2abbe9b4c0a75a36f6c8b0d615b6efdfd2ed60eb1195694426e57a5fd0a5c33d
Timestamp: 1782549414 Timestamp [UTC]: 2026-06-27 08:36:54 Age [y:d:h:m:s]: 00:146:00:40:48
Block: 1569088 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 113485 RingCT/type: yes/0
Extra: 012abbe9b4c0a75a36f6c8b0d615b6efdfd2ed60eb1195694426e57a5fd0a5c33d

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2ca3e37cf91b2ed18eff7c2029ca5a2e5b533151ce0eab1eb02c3b5aa03bcf20 0.000600000000 2059068 of 15 <56>

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": 1569098, "vin": [ { "gen": { "height": 1569088 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "2ca3e37cf91b2ed18eff7c2029ca5a2e5b533151ce0eab1eb02c3b5aa03bcf20", "view_tag": "56" } } } ], "extra": [ 1, 42, 187, 233, 180, 192, 167, 90, 54, 246, 200, 176, 214, 21, 182, 239, 223, 210, 237, 96, 235, 17, 149, 105, 68, 38, 229, 122, 95, 208, 165, 195, 61 ], "rct_signatures": { "type": 0 } }


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