← previous blocknext block →recent activity
Analyzing
Block #86,819,697
8 transactions · 7 stateful · 2026-07-10 10:22:18 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,819,697 · 8 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
1w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec2fb0b5…6db3
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xd2171a4a…a036
0x34b655…2a6f
4 touches
1 conflict
0x015c6c43…fa58
0x34b655…2a6f
4 touches
1 conflict
0x015c6c43…fa59
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x9b9caa88…69f3
0x34b655…2a6f
4 touches
1 conflict
0x8d888c90…5479
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 0xec2fb0b5f7…4e6db3
Audit this contract →
← previous block·next block →recent activity