← previous blocknext block →recent activity
Analyzing
Block #87,626,105
17 transactions · 16 stateful · 2026-07-14 04:15:03 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,626,105 · 17 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
1w02w14w06w17w08w010w111w212w313w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02fabc35…2769
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4a3
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4a4
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xd42fdceb…d869
0x34b655…2a6f
6 touches
3 conflicts
0x2af0c86b…def2
0x34b655…2a6f
6 touches
3 conflicts
0x8cca2254…7982
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
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
3 conflicts on slot 0x02fabc3504…2f2769
Audit this contract →
← previous block·next block →recent activity