Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a1db25c3187aa85b0c45d6e952e1f261d7b231afe62a07e55f22f09dcaf17ea

Tx prefix hash: 85a579eb7628aa5844a2711bca68c48a9aebf31c400eb8fcd891de5a93320d7e
Tx public key: 7fa977b9bf31da45c35b25f6b4e1e870026c447ec382167f10aed6752a055052
Timestamp: 1789949903 Timestamp [UTC]: 2026-09-21 00:18:23 Age [y:d:h:m:s]: 00:057:22:02:00
Block: 1639996 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 40688 RingCT/type: yes/0
Extra: 017fa977b9bf31da45c35b25f6b4e1e870026c447ec382167f10aed6752a055052

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 163a38b4143195ae41e04014b56f1882a2944a5721358749c23a5024d2e69971 0.000600000000 2130028 of 15 <b2>

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": 1640006, "vin": [ { "gen": { "height": 1639996 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "163a38b4143195ae41e04014b56f1882a2944a5721358749c23a5024d2e69971", "view_tag": "b2" } } } ], "extra": [ 1, 127, 169, 119, 185, 191, 49, 218, 69, 195, 91, 37, 246, 180, 225, 232, 112, 2, 108, 68, 126, 195, 130, 22, 127, 16, 174, 214, 117, 42, 5, 80, 82 ], "rct_signatures": { "type": 0 } }


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