← previous blocknext block →recent activity
Analyzing
Block #98,667,879
52 transactions · 49 stateful · 2026-08-24 04:50:13 UTC
Parallelism
69/100
Blocked
65%
Avg conflicts / tx
1.94
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #98,667,879 · 52 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w06w18w09w110w211w312w014w115w216w317w418w519w620w736w137w446w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
16 touches
28 conflicts
0x41755291…977f
0x065c9d…c394
10 touches
10 conflicts
0x002fed35…79fa
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x6d1b72ee…6b78
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
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
28 conflicts on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity