← previous blocknext block →recent activity
Analyzing
Block #99,745,197
22 transactions · 20 stateful · 2026-08-27 23:33:22 UTC
Parallelism
64/100
Blocked
50%
Avg conflicts / tx
1.73
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,745,197 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w111w215w216w317w419w520w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x92385428…6941
0x34b655…2a6f
16 touches
28 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
16 touches
28 conflicts
0x886db264…846e
0x34b655…2a6f
12 touches
15 conflicts
0xc65f46dd…513c
0x34b655…2a6f
8 touches
6 conflicts
0x792299c4…16b6
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x8cdd1279…7473
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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity