← previous blocknext block →recent activity
Analyzing
Block #86,830,033
13 transactions · 9 stateful · 2026-07-10 11:31:35 UTC
Parallelism
85/100
Blocked
11%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,830,033 · 13 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
2w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1728ed63…499c
0xea1b8e…c5ec
4 touches
1 conflict
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0x144f21e3…ba1d
0x1efe02…37d6
2 touches
0 conflicts
0xb7cbb23c…9a52
0x1efe02…37d6
2 touches
0 conflicts
0xeec0267b…723d
0x1efe02…37d6
2 touches
0 conflicts
0xcce2fd99…a8eb
0x3bd359…433a
2 touches
0 conflicts
0xf0f4d653…f15a
0x659bd0…a9da
2 touches
0 conflicts
0xf0f4d653…f15b
0x659bd0…a9da
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: LeverUp: LeverUp
1 conflict on slot 0x1728ed6317…a9499c
Audit this contract →
← previous block·next block →recent activity