← previous blocknext block →recent activity
Analyzing
Block #87,723,644
22 transactions · 19 stateful · 2026-07-14 15:07:27 UTC
Parallelism
82/100
Blocked
37%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,723,644 · 22 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
6w07w18w29w010w312w113w217w018w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbfb7adca…51d7
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x9427219b…5f2b
0x34b655…2a6f
6 touches
3 conflicts
0x81e1b637…2b3c
0x34b655…2a6f
4 touches
1 conflict
0x88fb89dd…f591
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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 0xbfb7adcac2…1751d7
Audit this contract →
← previous block·next block →recent activity