← previous blocknext block →recent activity
Analyzing
Block #88,083,018
20 transactions · 19 stateful · 2026-07-16 07:11:11 UTC
Parallelism
85/100
Blocked
47%
Avg conflicts / tx
0.7
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #88,083,018 · 20 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
1w02w14w05w17w08w19w110w011w112w213w214w216w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
6 touches
3 conflicts
0xd2253aeb…c307
0x0a2fbf…29b1
6 touches
3 conflicts
0xd2253aeb…c308
0x0a2fbf…29b1
6 touches
3 conflicts
0xda82a210…1c1a
0x0a2fbf…29b1
6 touches
3 conflicts
0xda82a210…1c1b
0x0a2fbf…29b1
6 touches
3 conflicts
0xda82a210…1c1e
0x0a2fbf…29b1
6 touches
3 conflicts
0x00000000…0005
0x370e2e…63b4
6 touches
3 conflicts
0xf19c29a6…bd9b
0x370e2e…63b4
6 touches
3 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: 0x0a2fbf2d…f729b1
3 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity