← previous blocknext block →recent activity
Analyzing
Block #87,904,107
18 transactions · 16 stateful · 2026-07-15 11:14:34 UTC
Parallelism
61/100
Blocked
50%
Avg conflicts / tx
1.39
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,904,107 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w16w27w38w49w510w612w013w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x461a3556…5948
0x34b655…2a6f
14 touches
21 conflicts
0x92385428…6941
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0xc36fa358…24cb
0x34b655…2a6f
10 touches
10 conflicts
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xfebaf6fc…61b5
0x34b655…2a6f
6 touches
3 conflicts
0x38e39eef…50bd
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
21 conflicts on slot 0x461a3556a1…3b5948
Audit this contract →
← previous block·next block →recent activity