← previous blocknext block →recent activity
Analyzing
Block #94,847,117
26 transactions · 23 stateful · 2026-08-10 18:30:03 UTC
Parallelism
69/100
Blocked
57%
Avg conflicts / tx
1.35
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #94,847,117 · 26 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w27w19w210w311w413w514w621w725w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac3bc39a…72e0
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x28ceceef…ecc2
0x34b655…2a6f
6 touches
3 conflicts
0x3b9bb58c…e73a
0x34b655…2a6f
6 touches
3 conflicts
0x840d3ab7…c8c4
0x34b655…2a6f
6 touches
3 conflicts
0xa558e115…fc88
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xac3bc39ab5…8572e0
Audit this contract →
← previous block·next block →recent activity