← previous blocknext block →recent activity
Analyzing
Block #87,355,115
11 transactions · 11 stateful · 2026-07-12 22:01:56 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,355,115 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7a11736c…64a0
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x8a35acfb…d1ad
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1ae
0xb1dbf0…c0d3
4 touches
1 conflict
0x118f9574…acfa
0xb1dbf0…c0d3
3 touches
1 conflict
0x64fccc04…8eab
0xb1dbf0…c0d3
3 touches
1 conflict
0x4ff21e31…8ed4
0x34b655…2a6f
2 touches
0 conflicts
0x8b7af792…9ef0
0x34b655…2a6f
2 touches
0 conflicts
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 0x7a11736c7c…8b64a0
Audit this contract →
← previous block·next block →recent activity