← previous blocknext block →recent activity
Analyzing
Block #94,207,232
21 transactions · 18 stateful · 2026-08-08 12:37:39 UTC
Parallelism
76/100
Blocked
50%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,207,232 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w06w17w28w39w011w114w215w017w318w420w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34a1ee7e…fb20
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0x278c4ae5…1639
0x34b655…2a6f
4 touches
1 conflict
0x32b804b3…ce18
0x34b655…2a6f
4 touches
1 conflict
0x40bc5adc…eda6
0x34b655…2a6f
4 touches
1 conflict
0x4bc1b6fd…ce27
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0x34a1ee7e95…7cfb20
Audit this contract →
← previous block·next block →recent activity