← previous blocknext block →recent activity
Analyzing
Block #94,230,508
14 transactions · 12 stateful · 2026-08-08 14:35:38 UTC
Parallelism
57/100
Blocked
58%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,230,508 · 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
4w05w16w27w38w111w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f4727d…cdb7
0x34b655…2a6f
6 touches
3 conflicts
0x5c16527f…628c
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x92132ed7…2722
0x34b655…2a6f
4 touches
1 conflict
0x228d47a0…0efa
0x34b655…2a6f
4 touches
1 conflict
0x91fff377…792b
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
3 conflicts on slot 0xf2f4727df6…a5cdb7
Audit this contract →
← previous block·next block →recent activity