← previous blocknext block →recent activity
Analyzing
Block #87,076,353
18 transactions · 17 stateful · 2026-07-11 14:57:32 UTC
Parallelism
78/100
Blocked
29%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,076,353 · 18 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
1w02w15w06w07w113w214w317w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb82620d6…032e
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xaf10e1bf…0391
0x34b655…2a6f
6 touches
3 conflicts
0x619c81de…01b4
0x34b655…2a6f
4 touches
1 conflict
0x76168e6c…6e1c
0x34b655…2a6f
4 touches
1 conflict
0x91ddc953…b712
0x34b655…2a6f
4 touches
1 conflict
0xae8ff4a3…733f
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 0xb82620d6b1…10032e
Audit this contract →
← previous block·next block →recent activity