← previous blocknext block →recent activity
Analyzing
Block #94,170,386
18 transactions · 15 stateful · 2026-08-08 09:30:53 UTC
Parallelism
61/100
Blocked
53%
Avg conflicts / tx
1.11
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,170,386 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w25w37w39w413w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
12 touches
15 conflicts
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0xeef37ed7…3606
0x34b655…2a6f
6 touches
3 conflicts
0x5502e1cc…3910
0x34b655…2a6f
6 touches
3 conflicts
0x4f1ad4b4…e00a
0x34b655…2a6f
4 touches
1 conflict
0x5ab74544…e16c
0x34b655…2a6f
4 touches
1 conflict
0x9ad325f5…cc43
0x34b655…2a6f
4 touches
1 conflict
0xa3ed5a09…c6d3
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
15 conflicts on slot 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity