← previous blocknext block →recent activity
Analyzing
Block #88,081,783
13 transactions · 12 stateful · 2026-07-16 07:02:56 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #88,081,783 · 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
2w03w14w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64e5f38d…187c
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xa1c4dc05…3d12
0x34b655…2a6f
4 touches
1 conflict
0x671e007b…1761
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0x23778a1f…dec4
0x34b655…2a6f
2 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
1 conflict on slot 0x64e5f38d50…20187c
Audit this contract →
← previous block·next block →recent activity