← previous blocknext block →recent activity
Analyzing
Block #87,058,832
15 transactions · 13 stateful · 2026-07-11 13:00:45 UTC
Parallelism
73/100
Blocked
31%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,058,832 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w18w29w312w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xc5decd02…dbf4
0x34b655…2a6f
6 touches
3 conflicts
0x00cd9338…40d2
0x34b655…2a6f
6 touches
3 conflicts
0x4a6982a4…158c
0x34b655…2a6f
4 touches
1 conflict
0x671886b7…46fe
0x34b655…2a6f
4 touches
1 conflict
0x6b71b2ba…c600
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4ab
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity