Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 873f60a2dc2d8f685a14e77d4b36ed40ac489c0ebbfb409a8d70be7b420ce6f9

Tx prefix hash: b243a6f1be52ea7a79401b8c0092c1c4c5deb7c7e0564fd0ed91221100bd451c
Tx public key: cc324a1b5b42f8781c84c53de42d18cace786153556271943c065016af7ec40f
Timestamp: 1764863560 Timestamp [UTC]: 2025-12-04 15:52:40 Age [y:d:h:m:s]: 00:345:10:02:31
Block: 1426381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252171 RingCT/type: yes/0
Extra: 01cc324a1b5b42f8781c84c53de42d18cace786153556271943c065016af7ec40f02110000000370609d03000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c25a1ef405c94fb4602f003a7490381930f94ca8e70a3779dead99f4a7339507 0.000600000000 1915072 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": 1426391, "vin": [ { "gen": { "height": 1426381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c25a1ef405c94fb4602f003a7490381930f94ca8e70a3779dead99f4a7339507" } } ], "extra": [ 1, 204, 50, 74, 27, 91, 66, 248, 120, 28, 132, 197, 61, 228, 45, 24, 202, 206, 120, 97, 83, 85, 98, 113, 148, 60, 6, 80, 22, 175, 126, 196, 15, 2, 17, 0, 0, 0, 3, 112, 96, 157, 3, 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: