Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a14fa5dc14d8e960eddebcc89bde92005dd5123a26a5a62db02062611355ad4

Tx prefix hash: 5f521154d71bb91aaa52146da2aa05d7a91a68f3ad9f911ec39da27ca0db7fe2
Tx public key: de85800dd4a4cb442c72013c8aaeffe4351eb60cf69fdbda990fe9e2b249a0bd
Timestamp: 1758363574 Timestamp [UTC]: 2025-09-20 10:19:34 Age [y:d:h:m:s]: 01:060:15:52:13
Block: 1372506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309818 RingCT/type: yes/0
Extra: 01de85800dd4a4cb442c72013c8aaeffe4351eb60cf69fdbda990fe9e2b249a0bd021100000003ad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7f9c68bc4f26a25c2327559671a10b0d7a9d6aac9489caee7276cf9f0bd92139 0.000600000000 1860591 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": 1372516, "vin": [ { "gen": { "height": 1372506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f9c68bc4f26a25c2327559671a10b0d7a9d6aac9489caee7276cf9f0bd92139" } } ], "extra": [ 1, 222, 133, 128, 13, 212, 164, 203, 68, 44, 114, 1, 60, 138, 174, 255, 228, 53, 30, 182, 12, 246, 159, 219, 218, 153, 15, 233, 226, 178, 73, 160, 189, 2, 17, 0, 0, 0, 3, 173, 121, 72, 208, 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: