← previous blocknext block →recent activity
Analyzing
Block #92,769,281
20 transactions · 18 stateful · 2026-08-03 12:01:07 UTC
Parallelism
60/100
Blocked
39%
Avg conflicts / tx
1.15
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #92,769,281 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w27w39w412w514w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xf06ab8d8…3589
0x34b655…2a6f
6 touches
3 conflicts
0x85eb1316…bb9e
0x34b655…2a6f
6 touches
3 conflicts
0xdd656078…a98c
0x34b655…2a6f
6 touches
3 conflicts
0xba9f88e8…9c33
0x34b655…2a6f
4 touches
1 conflict
0x4c04ce68…d007
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity