← previous blocknext block →recent activity
Analyzing
Block #94,301,179
14 transactions · 14 stateful · 2026-08-08 20:33:46 UTC
Parallelism
57/100
Blocked
57%
Avg conflicts / tx
1.43
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,301,179 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w06w17w28w39w210w311w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x11b69a7e…334e
0xee8c0e…1242
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0xa94c3b09…26c7
0x34b655…2a6f
6 touches
3 conflicts
0xdedfc336…f888
0x34b655…2a6f
6 touches
3 conflicts
0xa94c3b09…26c8
0x34b655…2a6f
6 touches
3 conflicts
0x03f717cd…62de
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity