← previous blocknext block →recent activity
Analyzing
Block #94,668,399
29 transactions · 26 stateful · 2026-08-10 03:29:35 UTC
Parallelism
86/100
Blocked
31%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,668,399 · 29 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
1w02w03w04w15w06w17w28w311w112w121w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xce06a0f7…efef
0x34b655…2a6f
6 touches
3 conflicts
0xdbc10be3…2d55
0x34b655…2a6f
5 touches
3 conflicts
0xf7ee61f5…f81a
0x34b655…2a6f
5 touches
3 conflicts
0x5502e1cc…3910
0x34b655…2a6f
4 touches
1 conflict
0x80398c66…f3cc
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 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity