← previous blocknext block →recent activity
Analyzing
Block #87,287,131
16 transactions · 14 stateful · 2026-07-12 14:27:22 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,287,131 · 16 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
1w02w15w08w010w112w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34bcdc05…6689
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xa7013be2…c0a8
0x34b655…2a6f
4 touches
1 conflict
0x9ad0eb5b…7a1b
0x34b655…2a6f
4 touches
1 conflict
0x66059cf4…bf4d
0x34b655…2a6f
4 touches
1 conflict
0x5d36316b…b0e4
0x34b655…2a6f
4 touches
1 conflict
0x05ec65f5…4eff
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
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 0x34bcdc05ee…2c6689
Audit this contract →
← previous block·next block →recent activity