← previous blocknext block →recent activity
Analyzing
Block #92,807,001
23 transactions · 19 stateful · 2026-08-03 15:10:56 UTC
Parallelism
74/100
Blocked
37%
Avg conflicts / tx
0.57
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #92,807,001 · 23 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
4w010w112w215w216w318w419w520w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xb3c96942…f0fc
0x34b655…2a6f
6 touches
3 conflicts
0x539ac47f…eb6f
0x34b655…2a6f
6 touches
3 conflicts
0x9a573905…60cf
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6b564d99…b9eb
0x34b655…2a6f
4 touches
1 conflict
0x6b564d99…b9ec
0x34b655…2a6f
4 touches
1 conflict
0x6dac0427…e0c2
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity