← previous blocknext block →recent activity
Analyzing
Block #88,078,222
12 transactions · 11 stateful · 2026-07-16 06:39:07 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #88,078,222 · 12 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
7w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6eff5416…605d
0xea1b8e…c5ec
4 touches
1 conflict
0xa8abcc19…3d83
0xea1b8e…c5ec
4 touches
1 conflict
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0x3dbd9177…e936
0xea1b8e…c5ec
3 touches
1 conflict
0x65994aff…d2ed
0x34b655…2a6f
2 touches
0 conflicts
0x65994aff…d2ee
0x34b655…2a6f
2 touches
0 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
2 touches
0 conflicts
0x8391fb68…4c83
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: LeverUp: LeverUp
1 conflict on slot 0x6eff5416ed…f5605d
Audit this contract →
← previous block·next block →recent activity