Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cafce1012d42faced37d740737498b65818eb5acd889a793de73853e39cebb7a

Tx prefix hash: a0e8ada66dbacfe90a380e25a032bbc953889cbbab1e374e7936b5e06f10819e
Tx public key: 8a25e11ae7be98ec0b9ad40a56fa2af88a2defd3c7432a0b1c639f36b740a7c4
Timestamp: 1745719884 Timestamp [UTC]: 2025-04-27 02:11:24 Age [y:d:h:m:s]: 01:014:19:42:18
Block: 1270271 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261358 RingCT/type: yes/0
Extra: 018a25e11ae7be98ec0b9ad40a56fa2af88a2defd3c7432a0b1c639f36b740a7c402110000000188cd2b63000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5fb39a51901ab87439789175c1fa5629f6b2c4fa6e3d432592eda075b581f72f 0.000600000000 1757512 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": 1270281, "vin": [ { "gen": { "height": 1270271 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5fb39a51901ab87439789175c1fa5629f6b2c4fa6e3d432592eda075b581f72f" } } ], "extra": [ 1, 138, 37, 225, 26, 231, 190, 152, 236, 11, 154, 212, 10, 86, 250, 42, 248, 138, 45, 239, 211, 199, 67, 42, 11, 28, 99, 159, 54, 183, 64, 167, 196, 2, 17, 0, 0, 0, 1, 136, 205, 43, 99, 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: