Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 339c629926ee90820086b3ffb4bfb7f0d7dd414e75d0dcdbbd9903097bf79dcf

Tx prefix hash: e9b446cc761b70084812e0675d4cec99d0985525d12d669f1c021b3356441291
Tx public key: e974619d4e1e708bbd6ae4bab25ad1b27dcb883ad8eee1ab986858382f776683
Timestamp: 1744285194 Timestamp [UTC]: 2025-04-10 11:39:54 Age [y:d:h:m:s]: 01:218:07:34:29
Block: 1258390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419962 RingCT/type: yes/0
Extra: 01e974619d4e1e708bbd6ae4bab25ad1b27dcb883ad8eee1ab986858382f7766830211000000066c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fc0baa373a0012a0fb74f2d696720ab0bac2f586a7623d69b95944653e34b437 0.000600000000 1745523 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": 1258400, "vin": [ { "gen": { "height": 1258390 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc0baa373a0012a0fb74f2d696720ab0bac2f586a7623d69b95944653e34b437" } } ], "extra": [ 1, 233, 116, 97, 157, 78, 30, 112, 139, 189, 106, 228, 186, 178, 90, 209, 178, 125, 203, 136, 58, 216, 238, 225, 171, 152, 104, 88, 56, 47, 119, 102, 131, 2, 17, 0, 0, 0, 6, 108, 152, 170, 61, 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: