← previous blocknext block →recent activity
Analyzing
Block #88,079,794
22 transactions · 18 stateful · 2026-07-16 06:49:38 UTC
Parallelism
86/100
Blocked
28%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #88,079,794 · 22 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
4w06w07w113w114w117w221w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa8abcc19…3d83
0xea1b8e…c5ec
4 touches
1 conflict
0xba5e0194…c391
0x34b655…2a6f
4 touches
1 conflict
0xbc5bd743…70f7
0x34b655…2a6f
4 touches
1 conflict
0xc80c0110…a968
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0dd44476…ef40
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x68e3283b…f417
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
1 conflict on slot 0xa8abcc1955…203d83
Audit this contract →
← previous block·next block →recent activity