← previous blocknext block →recent activity
Analyzing
Block #94,842,192
15 transactions · 14 stateful · 2026-08-10 18:05:15 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,842,192 · 15 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
2w03w14w07w28w310w412w314w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4abfb389…18f4
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0x021df0f6…5d6f
0x34b655…2a6f
8 touches
6 conflicts
0xbec23443…9293
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x4529cb27…8c5c
0x34b655…2a6f
4 touches
2 conflicts
0x793aa64d…b09c
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 0x4abfb3894a…c318f4
Audit this contract →
← previous block·next block →recent activity