← previous blocknext block →recent activity
Analyzing
Block #95,371,234
17 transactions · 17 stateful · 2026-08-12 14:39:02 UTC
Parallelism
71/100
Blocked
41%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,371,234 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w210w312w415w216w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b8368aa…9d5d
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x74137b07…5880
0x34b655…2a6f
6 touches
3 conflicts
0x673e2e56…9f5d
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xdc80e28a…b1ec
0x34b655…2a6f
4 touches
1 conflict
0x255aef4f…3968
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
3 conflicts on slot 0x7b8368aacf…cf9d5d
Audit this contract →
← previous block·next block →recent activity