← previous blocknext block →recent activity
Analyzing
Block #94,202,698
14 transactions · 14 stateful · 2026-08-08 12:14:43 UTC
Parallelism
64/100
Blocked
43%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,202,698 · 14 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
1w02w03w14w15w26w39w211w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x949fc5d9…55f3
0x34b655…2a6f
6 touches
3 conflicts
0xebb7c1dd…d826
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe2e52e46…0894
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xc13e1d5c…62c6
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
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
3 conflicts on slot 0x949fc5d98c…1955f3
Audit this contract →
← previous block·next block →recent activity