← previous blocknext block →recent activity
Analyzing
Block #87,913,395
13 transactions · 12 stateful · 2026-07-15 12:16:42 UTC
Parallelism
69/100
Blocked
42%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,913,395 · 13 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
1w02w14w05w16w29w311w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f6666e6…f280
0x34b655…2a6f
8 touches
6 conflicts
0x7139bf32…c881
0x34b655…2a6f
6 touches
3 conflicts
0x974c36fe…1cd7
0x34b655…2a6f
6 touches
3 conflicts
0x521553ff…d548
0x34b655…2a6f
4 touches
1 conflict
0x64aaadbf…f9f3
0x34b655…2a6f
4 touches
1 conflict
0x6e90b9b1…dca8
0x34b655…2a6f
4 touches
1 conflict
0x746bcce3…d0ce
0x34b655…2a6f
4 touches
1 conflict
0x76d36e11…fde2
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
6 conflicts on slot 0x0f6666e640…06f280
Audit this contract →
← previous block·next block →recent activity