← previous blocknext block →recent activity
Analyzing
Block #87,692,121
22 transactions · 20 stateful · 2026-07-14 11:36:12 UTC
Parallelism
77/100
Blocked
55%
Avg conflicts / tx
1.05
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,692,121 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w05w16w27w38w19w213w316w218w420w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d2c01c7…439f
0x34b655…2a6f
8 touches
6 conflicts
0x282fd1fa…1fca
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0x8a705be8…7ac4
0xc8689a…ee79
6 touches
3 conflicts
0xd35bb5ac…3586
0x065c9d…c394
6 touches
3 conflicts
0x09dddc76…e12a
0x34b655…2a6f
6 touches
3 conflicts
0x1a625167…f20e
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 0x5d2c01c7a7…64439f
Audit this contract →
← previous block·next block →recent activity