← previous blocknext block →recent activity
Analyzing
Block #95,217,571
23 transactions · 20 stateful · 2026-08-12 01:34:11 UTC
Parallelism
83/100
Blocked
40%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,217,571 · 23 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
1w04w05w17w08w09w111w012w113w214w015w116w117w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa779293b…5e59
0x34b655…2a6f
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x2b54cadb…4425
0xd18b7e…414b
6 touches
3 conflicts
0x4378e36b…c8e5
0x34b655…2a6f
4 touches
1 conflict
0x518aa708…c018
0x34b655…2a6f
4 touches
1 conflict
0x6e27bdfb…108a
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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: Perpl
6 conflicts on slot 0xa779293bef…815e59
Audit this contract →
← previous block·next block →recent activity