← previous blocknext block →recent activity
Analyzing
Block #87,713,117
20 transactions · 19 stateful · 2026-07-14 13:56:53 UTC
Parallelism
80/100
Blocked
37%
Avg conflicts / tx
0.8
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,713,117 · 20 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
1w02w04w15w26w311w112w215w319w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4f4af3b…c5bd
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
8 touches
6 conflicts
0x5170a218…3a84
0xc8689a…ee79
6 touches
3 conflicts
0x0ba865dd…a249
0x34b655…2a6f
6 touches
3 conflicts
0x2dc3cd56…c542
0x34b655…2a6f
6 touches
3 conflicts
0x74fd0a9b…3aaa
0x34b655…2a6f
6 touches
3 conflicts
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 0xf4f4af3b10…72c5bd
Audit this contract →
← previous block·next block →recent activity