Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a22a60c1ac8964b1ef83e7d3a34fbdde2b5cbcbdd2d9d340b0e5daadfa69f58a

Tx prefix hash: 6530cd6cf84647e8983e968495cbc2603d00b334f3b5e214ea53c92964dd0c03
Tx public key: ec7954492a8f96896df2dc5430c8fb16bc4ab48be59fce55afb4c0a8065eba34
Timestamp: 1742731827 Timestamp [UTC]: 2025-03-23 12:10:27 Age [y:d:h:m:s]: 01:239:18:18:12
Block: 1245542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 435394 RingCT/type: yes/0
Extra: 01ec7954492a8f96896df2dc5430c8fb16bc4ab48be59fce55afb4c0a8065eba34021100000006af845649000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c1834556a870fff182cb67c8c24a06ecd2d3b56475d783e19e981f00ed4a95fc 0.000600000000 1732533 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": 1245552, "vin": [ { "gen": { "height": 1245542 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1834556a870fff182cb67c8c24a06ecd2d3b56475d783e19e981f00ed4a95fc" } } ], "extra": [ 1, 236, 121, 84, 73, 42, 143, 150, 137, 109, 242, 220, 84, 48, 200, 251, 22, 188, 74, 180, 139, 229, 159, 206, 85, 175, 180, 192, 168, 6, 94, 186, 52, 2, 17, 0, 0, 0, 6, 175, 132, 86, 73, 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: