← previous blocknext block →recent activity
Analyzing
Block #86,735,097
17 transactions · 15 stateful · 2026-07-10 00:57:09 UTC
Parallelism
59/100
Blocked
47%
Avg conflicts / tx
1.29
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,735,097 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w36w48w010w511w113w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
14 touches
21 conflicts
0x0733be30…112f
0x34b655…2a6f
12 touches
15 conflicts
0xe718f3c7…c376
0x34b655…2a6f
6 touches
3 conflicts
0xcf090a80…4536
0x34b655…2a6f
6 touches
3 conflicts
0x2b3345cb…cb6b
0x34b655…2a6f
4 touches
1 conflict
0x41b014d9…6c12
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4d7e366b…7690
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
21 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity