← previous blocknext block →recent activity
Analyzing
Block #87,357,727
21 transactions · 19 stateful · 2026-07-12 22:19:23 UTC
Parallelism
76/100
Blocked
37%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,357,727 · 21 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
2w03w15w06w17w08w210w111w319w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb7e6d391…2f76
0x34b655…2a6f
8 touches
6 conflicts
0x0921c970…9f93
0x34b655…2a6f
4 touches
1 conflict
0x22c2bb0c…9d5d
0x34b655…2a6f
4 touches
1 conflict
0x5b9e5ecc…2bc7
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x93b6fab0…09d6
0x34b655…2a6f
4 touches
1 conflict
0x95c47f03…f1bb
0x34b655…2a6f
4 touches
1 conflict
0x8a35acfb…d1ac
0xb1dbf0…c0d3
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 0xb7e6d391a5…e42f76
Audit this contract →
← previous block·next block →recent activity