← previous blocknext block →recent activity
Analyzing
Block #87,727,296
27 transactions · 21 stateful · 2026-07-14 15:31:54 UTC
Parallelism
78/100
Blocked
57%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,727,296 · 27 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
1w02w03w14w25w06w17w18w010w114w015w218w119w220w021w322w125w426w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6000ba5…8d65
0x34b655…2a6f
8 touches
6 conflicts
0x3d381afb…8207
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x04fdea…47d7
6 touches
3 conflicts
0x7c93b38a…9e69
0x34b655…2a6f
4 touches
1 conflict
0x94ba9c4a…41d8
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 0xc6000ba5c1…988d65
Audit this contract →
← previous block·next block →recent activity