Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38e94cda13c0b045b65c8697ad0cac8e1c30b5ecfa321c33dbadf51aa1ab3e6c

Tx prefix hash: c95ba4ea3dd667d91b6c691021f26aef2ef004fd06534e3f2d91d909e63e6256
Tx public key: c8408e18111dc7bf5635f1226383f170c10bfac9ad1fe4c0c55041793250a8f6
Timestamp: 1752725795 Timestamp [UTC]: 2025-07-17 04:16:35 Age [y:d:h:m:s]: 01:120:14:31:54
Block: 1327166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351171 RingCT/type: yes/0
Extra: 01c8408e18111dc7bf5635f1226383f170c10bfac9ad1fe4c0c55041793250a8f60211000000032609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2a7cb5938e1f2581cee9ecc40fdbf9a476a3db55cf90262feaa6bd338ee2c846 0.000600000000 1814919 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": 1327176, "vin": [ { "gen": { "height": 1327166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a7cb5938e1f2581cee9ecc40fdbf9a476a3db55cf90262feaa6bd338ee2c846" } } ], "extra": [ 1, 200, 64, 142, 24, 17, 29, 199, 191, 86, 53, 241, 34, 99, 131, 241, 112, 193, 11, 250, 201, 173, 31, 228, 192, 197, 80, 65, 121, 50, 80, 168, 246, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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: