← previous blocknext block →recent activity
Analyzing
Block #94,859,898
16 transactions · 16 stateful · 2026-08-10 19:34:20 UTC
Parallelism
75/100
Blocked
50%
Avg conflicts / tx
1.13
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,859,898 · 16 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
1w02w03w14w25w06w17w29w210w111w312w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xecc655f1…34c8
0x34b655…2a6f
8 touches
6 conflicts
0xf5ea108a…dbf6
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x8e1318fe…3399
0x34b655…2a6f
4 touches
1 conflict
0xa3a621f8…75a2
0x34b655…2a6f
4 touches
1 conflict
0x0dd3d3cd…7281
0x34b655…2a6f
4 touches
1 conflict
0xc2403164…b6d3
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 0xecc655f12f…e934c8
Audit this contract →
← previous block·next block →recent activity