← previous blocknext block →recent activity
Analyzing
Block #86,856,678
16 transactions · 15 stateful · 2026-07-10 14:29:40 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,856,678 · 16 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
3w07w08w012w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf58b2d27…e4eb
0x34b655…2a6f
4 touches
1 conflict
0xb0446875…2b96
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x1e415003…6d34
0x34b655…2a6f
2 touches
0 conflicts
0x1ee44d08…7262
0x34b655…2a6f
2 touches
0 conflicts
0x301e1c77…9e30
0x34b655…2a6f
2 touches
0 conflicts
0x36810ff7…1728
0x34b655…2a6f
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 0xf58b2d270b…4ae4eb
Audit this contract →
← previous block·next block →recent activity