← previous blocknext block →recent activity
Analyzing
Block #92,853,973
19 transactions · 18 stateful · 2026-08-03 19:07:21 UTC
Parallelism
68/100
Blocked
44%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #92,853,973 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w16w17w28w39w311w413w117w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x28ceceef…ecc2
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xebac0f82…a49c
0x34b655…2a6f
6 touches
3 conflicts
0x383472f3…bdbc
0x34b655…2a6f
6 touches
3 conflicts
0x2be02b4b…59de
0x34b655…2a6f
4 touches
1 conflict
0x453a271e…8768
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
10 conflicts on slot 0x28ceceefb3…22ecc2
Audit this contract →
← previous block·next block →recent activity