← previous blocknext block →recent activity
Analyzing
Block #94,913,854
21 transactions · 20 stateful · 2026-08-11 00:05:41 UTC
Parallelism
62/100
Blocked
60%
Avg conflicts / tx
1.43
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #94,913,854 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w37w08w19w210w311w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41527b68…5ad4
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x11b69a7e…334e
0x01bff4…1071
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x08cc68a2…2a59
0x34b655…2a6f
6 touches
3 conflicts
0xa6c20caf…adf2
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x41527b689b…855ad4
Audit this contract →
← previous block·next block →recent activity