← previous blocknext block →recent activity
Analyzing
Block #86,127,268
17 transactions · 14 stateful · 2026-07-07 05:14:05 UTC
Parallelism
82/100
Blocked
43%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,127,268 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w18w011w112w215w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1728ed63…499c
0xea1b8e…c5ec
6 touches
3 conflicts
0x00bac013…a28c
0xfd44b3…00d1
6 touches
3 conflicts
0xdc409602…e3e4
0xd32edf…ff58
5 touches
3 conflicts
0xb6b74ae0…8d5e
0xea1b8e…c5ec
4 touches
1 conflict
0xc079cc93…b57b
0xea1b8e…c5ec
4 touches
1 conflict
0xa8abcc19…3d83
0xea1b8e…c5ec
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x172b0de5…980b
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: LeverUp: LeverUp
3 conflicts on slot 0x1728ed6317…a9499c
Audit this contract →
← previous block·next block →recent activity