← previous blocknext block →recent activity
Analyzing
Block #87,356,291
10 transactions · 9 stateful · 2026-07-12 22:09:48 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,356,291 · 10 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
1w02w15w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x135cdc1d…7b2f
0x34b655…2a6f
4 touches
1 conflict
0x42dd9d36…3fc0
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x606c8175…ca2b
0x40c49f…2af0
2 touches
0 conflicts
0x7fe32f39…1d04
0x40c49f…2af0
2 touches
0 conflicts
0xc32c5d45…6762
0x40c49f…2af0
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
1 conflict on slot 0x135cdc1dad…797b2f
Audit this contract →
← previous block·next block →recent activity