← previous blocknext block →recent activity
Analyzing
Block #88,351,504
46 transactions · 34 stateful · 2026-07-17 13:07:34 UTC
Parallelism
61/100
Blocked
68%
Avg conflicts / tx
2.15
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #88,351,504 · 46 txs across 18 waves · depth 18
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
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w16w210w012w116w017w118w219w320w422w423w524w635w836w938w1143w1644w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0xfb874a6c…caa0
0x34b655…2a6f
12 touches
15 conflicts
0xa6389d47…9a28
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xd6c45a31…9931
0x34b655…2a6f
8 touches
6 conflicts
0x0c9eb6ea…7c39
0x34b655…2a6f
8 touches
6 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
45 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity