← previous blocknext block →recent activity
Analyzing
Block #94,482,877
11 transactions · 8 stateful · 2026-08-09 11:56:28 UTC
Parallelism
73/100
Blocked
25%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,482,877 · 11 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
5w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0xc1f6acda…6abb
0x34b655…2a6f
4 touches
1 conflict
0x4c7c8c7f…d6fa
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x5451de01…be8e
0x34b655…2a6f
2 touches
0 conflicts
0x95ea33cc…0339
0x34b655…2a6f
2 touches
0 conflicts
0xbde524f4…43bf
0x34b655…2a6f
2 touches
0 conflicts
0xc799e56d…45aa
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity