← previous blocknext block →recent activity
Analyzing
Block #94,743,991
16 transactions · 14 stateful · 2026-08-10 09:50:36 UTC
Parallelism
50/100
Blocked
57%
Avg conflicts / tx
1.69
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #94,743,991 · 16 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
3w04w15w26w37w48w49w510w611w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa86bf682…81d0
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x80656e3b…9240
0x34b655…2a6f
8 touches
6 conflicts
0x4228eb58…8905
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x0ae8d56f…b875
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
21 conflicts on slot 0xa86bf6829e…df81d0
Audit this contract →
← previous block·next block →recent activity