← previous blocknext block →recent activity
Analyzing
Block #88,364,210
44 transactions · 37 stateful · 2026-07-17 14:33:11 UTC
Parallelism
68/100
Blocked
76%
Avg conflicts / tx
2.07
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #88,364,210 · 44 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w17w28w010w111w212w313w414w515w616w731w232w333w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xad0c145d…72b3
0xa6afd3…d132
6 touches
3 conflicts
0xb33ff823…1188
0x065c9d…c394
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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: 0x48cba278…e2b48b
28 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity