Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e70e193be765907807bbbed9c345265cbb3ca317cebf7d755dd93202cb144f3

Tx prefix hash: 20e699b3aa7e80c4e2ad4ab53d827a84e3aa9b46acbc688022674fce560ed9f0
Tx public key: ccd147edaa69ce53442d8126e4ef1d5f426cdaa717e33ad947f37c6b7dbed011
Timestamp: 1758171136 Timestamp [UTC]: 2025-09-18 04:52:16 Age [y:d:h:m:s]: 01:064:10:22:06
Block: 1370894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312595 RingCT/type: yes/0
Extra: 01ccd147edaa69ce53442d8126e4ef1d5f426cdaa717e33ad947f37c6b7dbed011021100000006b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 392ce45eaf1ec16856267953ea8a9a6189ff2767c4f5b70ff8a799c48289f15f 0.000600000000 1858971 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": 1370904, "vin": [ { "gen": { "height": 1370894 } } ], "vout": [ { "amount": 600000000, "target": { "key": "392ce45eaf1ec16856267953ea8a9a6189ff2767c4f5b70ff8a799c48289f15f" } } ], "extra": [ 1, 204, 209, 71, 237, 170, 105, 206, 83, 68, 45, 129, 38, 228, 239, 29, 95, 66, 108, 218, 167, 23, 227, 58, 217, 71, 243, 124, 107, 125, 190, 208, 17, 2, 17, 0, 0, 0, 6, 178, 247, 132, 196, 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: