← previous blocknext block →recent activity
Analyzing
Block #88,092,318
22 transactions · 18 stateful · 2026-07-16 08:13:24 UTC
Parallelism
77/100
Blocked
56%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,092,318 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w37w08w19w210w312w214w219w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x04fdea…47d7
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x734ee320…caae
0x34b655…2a6f
6 touches
3 conflicts
0xfe390f5b…42d9
0x34b655…2a6f
4 touches
1 conflict
0x9408df94…6750
0x34b655…2a6f
4 touches
1 conflict
0x982900c0…d7a7
0x34b655…2a6f
4 touches
1 conflict
0xa13535db…1162
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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: 0x04fdeac2…f747d7
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity