← previous blocknext block →recent activity
Analyzing
Block #98,672,332
85 transactions · 51 stateful · 2026-08-24 05:13:23 UTC
Parallelism
78/100
Blocked
76%
Avg conflicts / tx
2.56
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #98,672,332 · 85 txs across 19 waves · depth 19
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
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w26w07w08w112w114w015w116w217w318w421w524w627w730w831w934w255w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
34 touches
136 conflicts
0x889d5e90…929a
0x2a68ba…90c5
20 touches
45 conflicts
0x00000000…003d
0xa6afd3…d132
12 touches
15 conflicts
0xb26ff3de…9352
0xa6afd3…d132
12 touches
15 conflicts
0x5778d110…d2e6
0xc8689a…ee79
10 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
10 touches
10 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
8 touches
6 conflicts
0x8b780b26…f5ff
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
136 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity