← previous blocknext block →recent activity
Analyzing
Block #86,885,101
10 transactions · 9 stateful · 2026-07-10 17:39:45 UTC
Parallelism
60/100
Blocked
44%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,885,101 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb06917e8…6985
0x34b655…2a6f
6 touches
3 conflicts
0xf607560e…828a
0x34b655…2a6f
4 touches
1 conflict
0x97ea91d9…00b5
0x34b655…2a6f
4 touches
1 conflict
0xa7685db7…31aa
0x34b655…2a6f
4 touches
1 conflict
0xb0446875…2b96
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0d2e1791…c1dd
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 0xb06917e887…5e6985
Audit this contract →
← previous block·next block →recent activity