Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ab804fe849f4247fdc0c1ca108b28e2af4392141f89a0dc35cfb66858f3dcbe

Tx prefix hash: f52d52c19510f0629e8c2da1607866f8a6935ccd789f66566f5bfa84c7572643
Tx public key: 873a996c585afc2f08ea3b59f5bd6eb6e3c8d83427d6c7f3034798b89137e104
Timestamp: 1784438631 Timestamp [UTC]: 2026-07-19 05:23:51 Age [y:d:h:m:s]: 00:125:00:55:04
Block: 1585001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 98220 RingCT/type: yes/0
Extra: 01873a996c585afc2f08ea3b59f5bd6eb6e3c8d83427d6c7f3034798b89137e10402089a07c2e94512e65c

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: aa18497d2cf3d24a7841aabb7d7e61b7a6dc45f690f8b250be2196a9649f814b 0.000600000000 2074995 of 15 <2d>

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": 1585011, "vin": [ { "gen": { "height": 1585001 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "aa18497d2cf3d24a7841aabb7d7e61b7a6dc45f690f8b250be2196a9649f814b", "view_tag": "2d" } } } ], "extra": [ 1, 135, 58, 153, 108, 88, 90, 252, 47, 8, 234, 59, 89, 245, 189, 110, 182, 227, 200, 216, 52, 39, 214, 199, 243, 3, 71, 152, 184, 145, 55, 225, 4, 2, 8, 154, 7, 194, 233, 69, 18, 230, 92 ], "rct_signatures": { "type": 0 } }


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