← previous blocknext block →recent activity
Analyzing
Block #94,249,695
12 transactions · 11 stateful · 2026-08-08 16:13:03 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,249,695 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0xd8e0b04c…84d4
0x065c9d…c394
4 touches
1 conflict
0xf7adce63…0fd2
0x754704…b603
4 touches
1 conflict
0x8f361903…8677
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd4167a11…a19d
0x34b655…2a6f
4 touches
1 conflict
0xdac107e2…e2a8
0x34b655…2a6f
4 touches
1 conflict
0x4c1fbdf6…953d
0x754704…b603
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 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity