← previous blocknext block →recent activity
Analyzing
Block #94,235,549
10 transactions · 10 stateful · 2026-08-08 15:01:17 UTC
Parallelism
60/100
Blocked
30%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,235,549 · 10 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
1w03w15w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3651d66e…b5e9
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0x17abd0b1…f478
0x34b655…2a6f
4 touches
1 conflict
0xe5eb3c33…0e3a
0x34b655…2a6f
4 touches
1 conflict
0x1f90c45d…89c3
0x34b655…2a6f
2 touches
0 conflicts
0x2a1f7c09…2890
0x34b655…2a6f
2 touches
0 conflicts
0x320701d5…f9f3
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
6 conflicts on slot 0x3651d66e0d…9eb5e9
Audit this contract →
← previous block·next block →recent activity