← previous blocknext block →recent activity
Analyzing
Block #87,252,686
14 transactions · 13 stateful · 2026-07-12 10:37:01 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,252,686 · 14 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
1w02w16w07w18w211w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb7e686f…ac6b
0x34b655…2a6f
4 touches
1 conflict
0xc4ed41b1…6db5
0x34b655…2a6f
4 touches
1 conflict
0xef3343e5…1ad7
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x4f8a11e8…ae2d
0x34b655…2a6f
4 touches
1 conflict
0x5ff95106…7c15
0x34b655…2a6f
4 touches
1 conflict
0x5ff95106…7c16
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
1 conflict on slot 0xbb7e686fc7…b1ac6b
Audit this contract →
← previous block·next block →recent activity