← previous blocknext block →recent activity
Analyzing
Block #87,663,168
15 transactions · 11 stateful · 2026-07-14 08:22:43 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,663,168 · 15 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
4w05w16w17w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe197e523…ef9c
0x34b655…2a6f
6 touches
3 conflicts
0x10ef891f…d726
0x34b655…2a6f
4 touches
1 conflict
0x3c78ca04…432c
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x62030a81…91be
0x34b655…2a6f
4 touches
1 conflict
0x62b13313…bbe8
0x34b655…2a6f
4 touches
1 conflict
0x6519ceab…86d2
0x34b655…2a6f
4 touches
1 conflict
0x6ba89834…1826
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 0xe197e52366…87ef9c
Audit this contract →
← previous block·next block →recent activity