← previous blocknext block →recent activity
Analyzing
Block #86,691,844
21 transactions · 18 stateful · 2026-07-09 20:08:20 UTC
Parallelism
81/100
Blocked
28%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,691,844 · 21 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
1w02w16w010w213w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xccdc32f8…72be
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x676d5418…85ea
0x34b655…2a6f
6 touches
3 conflicts
0x01df0928…3426
0x34b655…2a6f
6 touches
3 conflicts
0x01df0928…3427
0x34b655…2a6f
6 touches
3 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
6 touches
3 conflicts
0x0b320394…cc69
0x34b655…2a6f
6 touches
3 conflicts
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 0xccdc32f871…9a72be
Audit this contract →
← previous block·next block →recent activity