← previous blocknext block →recent activity
Analyzing
Block #92,538,333
15 transactions · 13 stateful · 2026-08-02 16:38:21 UTC
Parallelism
73/100
Blocked
38%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,538,333 · 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
4w05w16w28w09w110w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa0d3a786…91d9
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xaf19c45c…d1a8
0x34b655…2a6f
4 touches
1 conflict
0xaf19c45c…d1a9
0x34b655…2a6f
4 touches
1 conflict
0xb3fc3df4…b5fb
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc0a11fcc…5880
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 0xa0d3a786de…b991d9
Audit this contract →
← previous block·next block →recent activity