← previous blocknext block →recent activity
Analyzing
Block #87,052,477
14 transactions · 13 stateful · 2026-07-11 12:18:14 UTC
Parallelism
64/100
Blocked
31%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,052,477 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x9199a85a…acd9
0x34b655…2a6f
8 touches
6 conflicts
0xdb88134d…d6c1
0x34b655…2a6f
4 touches
1 conflict
0xdb88134d…d6c2
0x34b655…2a6f
4 touches
1 conflict
0xc1731a2d…f9fe
0x34b655…2a6f
4 touches
1 conflict
0x59c89f2b…2f10
0x34b655…2a6f
4 touches
1 conflict
0xe8807992…97a3
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 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity