Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c606cb65db71f1e426c37ad0fd0cc68f9404f2b2f3cf606f9638c855fc441531

Tx prefix hash: 1d1733df74b32a6e7725eb5fb04f538e27d78e300e8a1d42ee836ebbdd52e967
Tx public key: 524476df6f553c5eba2e395295612e89ddd81ada7221f5111cb6e89fb9b91a6d
Timestamp: 1746588216 Timestamp [UTC]: 2025-05-07 03:23:36 Age [y:d:h:m:s]: 01:198:00:22:18
Block: 1277455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405687 RingCT/type: yes/0
Extra: 01524476df6f553c5eba2e395295612e89ddd81ada7221f5111cb6e89fb9b91a6d0211000000011f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a4a57c3a3ebae6ea4d22e6059ce44f3becd91892bbcc1a22471b366fdceaeb6f 0.000600000000 1764810 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": 1277465, "vin": [ { "gen": { "height": 1277455 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4a57c3a3ebae6ea4d22e6059ce44f3becd91892bbcc1a22471b366fdceaeb6f" } } ], "extra": [ 1, 82, 68, 118, 223, 111, 85, 60, 94, 186, 46, 57, 82, 149, 97, 46, 137, 221, 216, 26, 218, 114, 33, 245, 17, 28, 182, 232, 159, 185, 185, 26, 109, 2, 17, 0, 0, 0, 1, 31, 144, 81, 122, 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: