← previous blocknext block →recent activity
Analyzing
Block #94,198,842
7 transactions · 7 stateful · 2026-08-08 11:55:15 UTC
Parallelism
43/100
Blocked
43%
Avg conflicts / tx
0.86
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,198,842 · 7 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
1w02w13w25w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x8299fe6c…5752
0x34b655…2a6f
4 touches
1 conflict
0x1f90c45d…89c3
0x34b655…2a6f
4 touches
1 conflict
0x5d4a544d…41f3
0x34b655…2a6f
4 touches
1 conflict
0x17b720f5…ad7a
0x34b655…2a6f
2 touches
0 conflicts
0x1e137b39…bae2
0x34b655…2a6f
2 touches
0 conflicts
0x1e5a992d…d114
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity