← previous blocknext block →recent activity
Analyzing
Block #86,847,086
19 transactions · 13 stateful · 2026-07-10 13:25:32 UTC
Parallelism
84/100
Blocked
31%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,847,086 · 19 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
1w03w18w09w110w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xa139e1f5…bed2
0x34b655…2a6f
4 touches
1 conflict
0xa9df6131…bf9a
0x34b655…2a6f
4 touches
1 conflict
0x013c31f5…a717
0x34b655…2a6f
4 touches
1 conflict
0x013c31f5…a718
0x34b655…2a6f
4 touches
1 conflict
0x0921c970…9f93
0x34b655…2a6f
4 touches
1 conflict
0xc7fed9f9…f3a0
0x34b655…2a6f
4 touches
1 conflict
0x39138a6c…239c
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity