← previous blocknext block →recent activity
Analyzing
Block #99,983,034
55 transactions · 41 stateful · 2026-08-28 19:34:54 UTC
Parallelism
65/100
Blocked
71%
Avg conflicts / tx
2.05
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #99,983,034 · 55 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
4w05w110w011w112w213w014w125w227w228w329w430w532w135w639w342w449w1351w1553w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0x451e482b…7e7d
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x0f778efb…51c3
0xd32edf…ff58
7 touches
6 conflicts
0x5f46663c…b4c2
0x34b655…2a6f
6 touches
3 conflicts
0x62910921…3016
0x34b655…2a6f
6 touches
3 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