← previous blocknext block →recent activity
Analyzing
Block #95,031,942
20 transactions · 17 stateful · 2026-08-11 09:59:40 UTC
Parallelism
90/100
Blocked
18%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,031,942 · 20 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w07w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91b0f8ed…6bd6
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x7d741885…3a6b
0xd32edf…ff58
3 touches
1 conflict
0x0d797812…95c0
0x065c9d…c394
2 touches
0 conflicts
0x83c0f749…fb6a
0x065c9d…c394
2 touches
0 conflicts
0xa7d6ba23…3f36
0x065c9d…c394
2 touches
0 conflicts
0xae07c61c…a4e3
0x065c9d…c394
2 touches
0 conflicts
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
1 conflict on slot 0x91b0f8edc5…b76bd6
Audit this contract →
← previous block·next block →recent activity