← previous blocknext block →recent activity
Analyzing
Block #99,284,358
32 transactions · 27 stateful · 2026-08-26 08:44:04 UTC
Parallelism
88/100
Blocked
41%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,284,358 · 32 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w07w08w19w010w113w217w018w022w224w126w127w329w130w131w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x348fda08…7e96
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xba38536d…2b7d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
6 touches
3 conflicts
0x631b4113…baa9
0x34b655…2a6f
6 touches
3 conflicts
0xa605468c…1bfc
0x2b46c0…1669
4 touches
1 conflict
0xc8525006…2b45
0x2b46c0…1669
4 touches
1 conflict
0x57330c5d…9973
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Kuru Exchange: Market-MON/USDC
6 conflicts on slot 0x348fda08cf…fc7e96
Audit this contract →
← previous block·next block →recent activity