← previous blocknext block →recent activity
Analyzing
Block #99,700,067
43 transactions · 41 stateful · 2026-08-27 19:45:12 UTC
Parallelism
67/100
Blocked
63%
Avg conflicts / tx
1.74
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #99,700,067 · 43 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w17w18w212w013w014w215w116w217w318w429w531w632w733w134w236w742w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x5da92df7…74b5
0x34b655…2a6f
8 touches
6 conflicts
0x57e5abc1…286f
0x34b655…2a6f
6 touches
3 conflicts
0x63726607…4e47
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
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
28 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity