← previous blocknext block →recent activity
Analyzing
Block #86,978,764
10 transactions · 9 stateful · 2026-07-11 04:05:41 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,978,764 · 10 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
1w02w16w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6083af24…a0df
0x34b655…2a6f
4 touches
1 conflict
0x65e6e603…cb45
0x34b655…2a6f
4 touches
1 conflict
0x7840c762…8060
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
0x2b95e778…d7d0
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
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 0x6083af2440…5fa0df
Audit this contract →
← previous block·next block →recent activity