← previous blocknext block →recent activity
Analyzing
Block #94,717,636
18 transactions · 17 stateful · 2026-08-10 07:37:14 UTC
Parallelism
78/100
Blocked
47%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,717,636 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w07w18w19w210w312w013w114w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7685db7…31aa
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xf607560e…828a
0x34b655…2a6f
6 touches
3 conflicts
0xa3f6f7c8…2436
0x34b655…2a6f
6 touches
3 conflicts
0x011251ba…598a
0x34b655…2a6f
6 touches
3 conflicts
0xee75c266…f8c6
0x34b655…2a6f
6 touches
3 conflicts
0xa97d4a89…ea5b
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
6 conflicts on slot 0xa7685db7f5…e331aa
Audit this contract →
← previous block·next block →recent activity