← previous blocknext block →recent activity
Analyzing
Block #87,626,405
17 transactions · 17 stateful · 2026-07-14 04:17:03 UTC
Parallelism
65/100
Blocked
47%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,626,405 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w39w410w112w514w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc8304415…4f91
0x34b655…2a6f
6 touches
3 conflicts
0x008accc4…1da7
0x34b655…2a6f
4 touches
1 conflict
0x008accc4…1da8
0x34b655…2a6f
4 touches
1 conflict
0x2a6511de…28dd
0x34b655…2a6f
4 touches
1 conflict
0x2c37de6b…04c6
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4be9812b…48a9
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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 0xc8304415c6…574f91
Audit this contract →
← previous block·next block →recent activity