← previous blocknext block →recent activity
Analyzing
Block #98,673,956
62 transactions · 51 stateful · 2026-08-24 05:21:52 UTC
Parallelism
63/100
Blocked
69%
Avg conflicts / tx
4.53
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #98,673,956 · 62 txs across 23 waves · depth 23
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
wave w19
wave w20
wave w21
wave w22
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w015w016w117w218w319w420w521w622w725w126w235w837w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
42 touches
210 conflicts
0x00000000…003d
0xa6afd3…d132
18 touches
36 conflicts
0x737acb78…fce8
0x34b655…2a6f
16 touches
28 conflicts
0x889d5e90…929a
0x2a68ba…90c5
16 touches
28 conflicts
0xf8f1e808…a4fd
0x34b655…2a6f
16 touches
28 conflicts
0xac2a0273…721b
0x34b655…2a6f
16 touches
28 conflicts
0x5778d110…d2e6
0xc8689a…ee79
14 touches
21 conflicts
0x3f2100d8…f9b5
0xa6afd3…d132
14 touches
21 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
210 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity