Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13ee3a721680dc2fd1d880a4b3b7fa92fcc2719d591849e0fe6f95e643cbb57c

Tx prefix hash: 9ba9faaf1d06d6130e7d17ee7d020b60c1135a1c068de4541906ec18e4c24671
Tx public key: b744920adb02bffdb6e452b3c5286c821dc8792ea6f0fcd132fce52e00d23799
Timestamp: 1745758164 Timestamp [UTC]: 2025-04-27 12:49:24 Age [y:d:h:m:s]: 01:205:11:09:59
Block: 1270591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 410897 RingCT/type: yes/0
Extra: 01b744920adb02bffdb6e452b3c5286c821dc8792ea6f0fcd132fce52e00d237990211000000079f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c795cc32f2c75b60e3500004dd32a15a8e0e3d2327b8d580a7e64866150a4ace 0.000600000000 1757834 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": 1270601, "vin": [ { "gen": { "height": 1270591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c795cc32f2c75b60e3500004dd32a15a8e0e3d2327b8d580a7e64866150a4ace" } } ], "extra": [ 1, 183, 68, 146, 10, 219, 2, 191, 253, 182, 228, 82, 179, 197, 40, 108, 130, 29, 200, 121, 46, 166, 240, 252, 209, 50, 252, 229, 46, 0, 210, 55, 153, 2, 17, 0, 0, 0, 7, 159, 159, 230, 140, 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: