Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2d34e0d0969cf1e6951c3767190adaa4c7e5b3bd7ed776e65f0e117a134fc3a

Tx prefix hash: 023a76f9f489defe45f4bc863b69a278fda8988b51951aac7c526ce76100faa3
Tx public key: 065af8041a42556751c7284dc519f58aab9921b4a01c0c744ff469b68c3fed23
Timestamp: 1745277658 Timestamp [UTC]: 2025-04-21 23:20:58 Age [y:d:h:m:s]: 01:213:05:21:41
Block: 1266601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416571 RingCT/type: yes/0
Extra: 01065af8041a42556751c7284dc519f58aab9921b4a01c0c744ff469b68c3fed230211000000026c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 148b5e5703f7fba9091b7ca55e0e5f9ba335fefc8df48fdd16fa62920590242d 0.000600000000 1753822 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": 1266611, "vin": [ { "gen": { "height": 1266601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "148b5e5703f7fba9091b7ca55e0e5f9ba335fefc8df48fdd16fa62920590242d" } } ], "extra": [ 1, 6, 90, 248, 4, 26, 66, 85, 103, 81, 199, 40, 77, 197, 25, 245, 138, 171, 153, 33, 180, 160, 28, 12, 116, 79, 244, 105, 182, 140, 63, 237, 35, 2, 17, 0, 0, 0, 2, 108, 152, 170, 61, 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: