← previous blocknext block →recent activity
Analyzing
Block #88,364,729
33 transactions · 31 stateful · 2026-07-17 14:36:43 UTC
Parallelism
55/100
Blocked
68%
Avg conflicts / tx
3.55
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #88,364,729 · 33 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w38w09w110w212w313w414w515w616w717w818w919w1020w1121w1222w1323w1424w429w232w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
30 touches
105 conflicts
0x6ed0779d…19a6
0x0a2fbf…29b1
30 touches
105 conflicts
0x6ed0779d…19a7
0x0a2fbf…29b1
30 touches
105 conflicts
0xdc26b069…0bdf
0x0a2fbf…29b1
30 touches
105 conflicts
0xdc26b069…0be0
0x0a2fbf…29b1
30 touches
105 conflicts
0xdc26b069…0be3
0x0a2fbf…29b1
30 touches
105 conflicts
0x00000000…0005
0x370e2e…63b4
30 touches
105 conflicts
0x1bff683e…7ecb
0x754704…b603
30 touches
105 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
105 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity