← previous blocknext block →recent activity
Analyzing
Block #92,760,064
15 transactions · 11 stateful · 2026-08-03 11:14:43 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,760,064 · 15 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
1w02w16w07w18w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c04ce68…d007
0x34b655…2a6f
6 touches
3 conflicts
0x0110331c…b891
0x34b655…2a6f
4 touches
1 conflict
0x0492d321…6e89
0x34b655…2a6f
4 touches
1 conflict
0x1eb0fab5…3517
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xf8e84422…84a6
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x59a54ff4…d21b
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 0x4c04ce6804…bbd007
Audit this contract →
← previous block·next block →recent activity