Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aaa3f91c590eebd249bb915a02a06cf979921c190e84b4491a3e28ea8d0cb40e

Tx prefix hash: f00af28c97c950c2ac9563390bb826beb3f90c1573dd4590a6df84b0a1c860f3
Tx public key: 438bc09df049a0bccf4a9f1eff71c8a7c4e45d7b7fb0957c6101b82c325f8682
Timestamp: 1773547661 Timestamp [UTC]: 2026-03-15 04:07:41 Age [y:d:h:m:s]: 00:244:07:58:13
Block: 1498116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180005 RingCT/type: yes/0
Extra: 01438bc09df049a0bccf4a9f1eff71c8a7c4e45d7b7fb0957c6101b82c325f8682021100000009e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d001da82bfef744b7599d2612a6750b0b193aee43b8da1f9dee1aacea164ad25 0.000600000000 1987762 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": 1498126, "vin": [ { "gen": { "height": 1498116 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d001da82bfef744b7599d2612a6750b0b193aee43b8da1f9dee1aacea164ad25" } } ], "extra": [ 1, 67, 139, 192, 157, 240, 73, 160, 188, 207, 74, 159, 30, 255, 113, 200, 167, 196, 228, 93, 123, 127, 176, 149, 124, 97, 1, 184, 44, 50, 95, 134, 130, 2, 17, 0, 0, 0, 9, 228, 245, 25, 63, 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: