Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac197d5cbef918d827534a6c45be9e72efbf0d4840e5ef795d8dc910a96ea22e

Tx prefix hash: 3a99e9f66ec41c5b3473de9197280587a3e07edca4664180597a5907548668d9
Tx public key: 0e66ae48434845e0323fe153f333d5a1e76f4dab4715c4b4c09085a204b32ca2
Timestamp: 1774138617 Timestamp [UTC]: 2026-03-22 00:16:57 Age [y:d:h:m:s]: 00:239:00:57:53
Block: 1502979 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176313 RingCT/type: yes/0
Extra: 010e66ae48434845e0323fe153f333d5a1e76f4dab4715c4b4c09085a204b32ca2021100000004f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: afd57f63e6ae5d93edb0638c66c8bc7742d5aeef7ceba2ba9a796e6d25bca474 0.000600000000 1992683 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": 1502989, "vin": [ { "gen": { "height": 1502979 } } ], "vout": [ { "amount": 600000000, "target": { "key": "afd57f63e6ae5d93edb0638c66c8bc7742d5aeef7ceba2ba9a796e6d25bca474" } } ], "extra": [ 1, 14, 102, 174, 72, 67, 72, 69, 224, 50, 63, 225, 83, 243, 51, 213, 161, 231, 111, 77, 171, 71, 21, 196, 180, 192, 144, 133, 162, 4, 179, 44, 162, 2, 17, 0, 0, 0, 4, 241, 136, 200, 168, 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: