← previous blocknext block →recent activity
Analyzing
Block #88,088,769
13 transactions · 13 stateful · 2026-07-16 07:49:39 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #88,088,769 · 13 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
2w03w14w08w09w110w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5777bd87…71bd
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4a1
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9417
0x34b655…2a6f
4 touches
1 conflict
0x23851631…90e4
0x34b655…2a6f
4 touches
1 conflict
0x13510de3…1c68
0x34b655…2a6f
2 touches
0 conflicts
0x201679bc…0414
0x34b655…2a6f
2 touches
0 conflicts
0x3726966a…669d
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: Perpl
3 conflicts on slot 0x5777bd874f…7071bd
Audit this contract →
← previous block·next block →recent activity