← previous blocknext block →recent activity
Analyzing
Block #87,076,794
14 transactions · 11 stateful · 2026-07-11 15:00:28 UTC
Parallelism
64/100
Blocked
55%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,076,794 · 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
2w03w17w28w39w412w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1175233a…64e7
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x140ef734…f17f
0x34b655…2a6f
4 touches
1 conflict
0x1629a29f…4701
0x34b655…2a6f
4 touches
1 conflict
0x6f2f2506…2a91
0x34b655…2a6f
4 touches
1 conflict
0x7506443a…4820
0x34b655…2a6f
4 touches
1 conflict
0x7523ad90…2ba5
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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
3 conflicts on slot 0x1175233a5a…bb64e7
Audit this contract →
← previous block·next block →recent activity