← previous blocknext block →recent activity
Analyzing
Block #86,982,217
18 transactions · 16 stateful · 2026-07-11 04:28:47 UTC
Parallelism
89/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,982,217 · 18 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w08w010w111w113w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe35b84bc…4d5b
0x34b655…2a6f
4 touches
1 conflict
0x155dff63…2af8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x856d2776…04c9
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xa46242d8…c0a8
0x34b655…2a6f
4 touches
1 conflict
0xbc96083d…124d
0x34b655…2a6f
4 touches
1 conflict
0xdbd174e4…b6f8
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 0xe35b84bcc8…124d5b
Audit this contract →
← previous block·next block →recent activity