Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 790de334353b88306ea2ed7a94b4bea5c013418a424fafcd090a00a20ac942ae

Tx prefix hash: e63737eed945109d1dead29e7d09a1d94e2b24a5ef4cee2a84846ca71901738f
Tx public key: 408b0760e7c1fdef219c97d05a467c63d701ab49e3e1dbcd7b987ae70089e40a
Timestamp: 1772825110 Timestamp [UTC]: 2026-03-06 19:25:10 Age [y:d:h:m:s]: 00:260:16:28:26
Block: 1492134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191360 RingCT/type: yes/0
Extra: 01408b0760e7c1fdef219c97d05a467c63d701ab49e3e1dbcd7b987ae70089e40a021100000007f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5ec141ef8296c1acbbfdbca015787a451fd40b56bba0944ea39d5304c79b4d46 0.000600000000 1981672 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": 1492144, "vin": [ { "gen": { "height": 1492134 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ec141ef8296c1acbbfdbca015787a451fd40b56bba0944ea39d5304c79b4d46" } } ], "extra": [ 1, 64, 139, 7, 96, 231, 193, 253, 239, 33, 156, 151, 208, 90, 70, 124, 99, 215, 1, 171, 73, 227, 225, 219, 205, 123, 152, 122, 231, 0, 137, 228, 10, 2, 17, 0, 0, 0, 7, 241, 136, 200, 168, 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: