← previous blocknext block →recent activity
Analyzing
Block #86,830,938
17 transactions · 13 stateful · 2026-07-10 11:37:38 UTC
Parallelism
76/100
Blocked
31%
Avg conflicts / tx
0.24
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,830,938 · 17 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
2w03w16w28w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d888c90…5479
0x34b655…2a6f
4 touches
1 conflict
0x8eed7e30…c1ef
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xbca4de0c…577c
0x34b655…2a6f
4 touches
1 conflict
0xc92cdb89…7078
0x34b655…2a6f
4 touches
1 conflict
0xfebaf6fc…61b5
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xd1ec0dfd…ccc0
0xc8689a…ee79
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 0x8d888c9003…aa5479
Audit this contract →
← previous block·next block →recent activity