← previous blocknext block →recent activity
Analyzing
Block #87,076,730
22 transactions · 19 stateful · 2026-07-11 15:00:03 UTC
Parallelism
77/100
Blocked
26%
Avg conflicts / tx
0.45
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,076,730 · 22 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
5w06w19w014w015w119w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3e06ffb…6c2b
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x1b40cab2…5253
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x396be562…a54a
0x34b655…2a6f
4 touches
1 conflict
0x3e56ba2d…6713
0x34b655…2a6f
4 touches
1 conflict
0x5379f516…8bf2
0x34b655…2a6f
4 touches
1 conflict
0x7506443a…4820
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 0xa3e06ffb4c…916c2b
Audit this contract →
← previous block·next block →recent activity