Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbf765fbb1d1508a38cd1501dcf8124bce1245a4e2909122bfdc73bc3806fb6e

Tx prefix hash: c490c11127811156622da3798d06148562ab4a9c8a7e9f4f3c2ce3c9f8754098
Tx public key: 4145faf59dd6834b9eaa22d84f3d3ae4388e771961ef1aa800c51a80464e3428
Timestamp: 1761762640 Timestamp [UTC]: 2025-10-29 18:30:40 Age [y:d:h:m:s]: 01:016:16:45:25
Block: 1400678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278174 RingCT/type: yes/0
Extra: 014145faf59dd6834b9eaa22d84f3d3ae4388e771961ef1aa800c51a80464e342802110000000225a35a0f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6ac38d0b333c5628edea2481b1ee1a520b2e2ebb7a6473e747d8708c563920d5 0.000600000000 1888995 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": 1400688, "vin": [ { "gen": { "height": 1400678 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ac38d0b333c5628edea2481b1ee1a520b2e2ebb7a6473e747d8708c563920d5" } } ], "extra": [ 1, 65, 69, 250, 245, 157, 214, 131, 75, 158, 170, 34, 216, 79, 61, 58, 228, 56, 142, 119, 25, 97, 239, 26, 168, 0, 197, 26, 128, 70, 78, 52, 40, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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: