← previous blocknext block →recent activity
Analyzing
Block #98,391,306
54 transactions · 37 stateful · 2026-08-23 05:07:42 UTC
Parallelism
65/100
Blocked
70%
Avg conflicts / tx
2.78
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #98,391,306 · 54 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
17w018w019w120w221w322w423w524w633w634w237w543w846w1150w1553w18
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
28 touches
91 conflicts
0x889d5e90…929a
0x2a68ba…90c5
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
12 touches
15 conflicts
0x5095cb33…2491
0xa6afd3…d132
10 touches
10 conflicts
0x5ea8c657…71b9
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 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
91 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity