← previous blocknext block →recent activity
Analyzing
Block #92,447,150
12 transactions · 12 stateful · 2026-08-02 08:59:43 UTC
Parallelism
67/100
Blocked
42%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,447,150 · 12 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
1w04w15w26w37w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x096c7f83…68af
0x34b655…2a6f
4 touches
1 conflict
0x1b287091…65ac
0x34b655…2a6f
4 touches
1 conflict
0x1eb0fab5…3517
0x34b655…2a6f
4 touches
1 conflict
0x2ad29b13…92e0
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x50e54461…beba
0x34b655…2a6f
4 touches
1 conflict
0x5d3bb355…4549
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
1 conflict on slot 0x096c7f8372…5e68af
Audit this contract →
← previous block·next block →recent activity