← previous blocknext block →recent activity
Analyzing
Block #87,293,336
14 transactions · 12 stateful · 2026-07-12 15:08:53 UTC
Parallelism
64/100
Blocked
33%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,293,336 · 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
2w03w14w26w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa9f59232…f58c
0x34b655…2a6f
6 touches
3 conflicts
0x2b7950c1…2342
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x0a6a5b44…d0e5
0x34b655…2a6f
4 touches
1 conflict
0x22eedaf2…c7b9
0x34b655…2a6f
4 touches
1 conflict
0x235d4827…ef4b
0x34b655…2a6f
4 touches
1 conflict
0x2817b4b4…8a4f
0x34b655…2a6f
4 touches
1 conflict
0x3ef0952c…762d
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 0xa9f59232f9…53f58c
Audit this contract →
← previous block·next block →recent activity