← previous blocknext block →recent activity
Analyzing
Block #87,077,722
20 transactions · 19 stateful · 2026-07-11 15:06:41 UTC
Parallelism
75/100
Blocked
42%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,077,722 · 20 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
1w02w15w06w07w19w210w211w312w416w317w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x17fff7d7…7b99
0x34b655…2a6f
4 touches
1 conflict
0x17fff7d7…7b9a
0x34b655…2a6f
4 touches
1 conflict
0x19c056c4…8ee3
0x34b655…2a6f
4 touches
1 conflict
0x2029b74e…c206
0x34b655…2a6f
4 touches
1 conflict
0x5ece8f90…f4c5
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