← previous blocknext block →recent activity
Analyzing
Block #99,780,417
22 transactions · 21 stateful · 2026-08-28 02:32:08 UTC
Parallelism
64/100
Blocked
43%
Avg conflicts / tx
1.64
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,780,417 · 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
5w06w07w18w010w111w115w016w217w318w419w520w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xb409e204…89ac
0x34b655…2a6f
12 touches
15 conflicts
0x537e2e5b…c3ab
0x34b655…2a6f
7 touches
6 conflicts
0xa9d11061…b7e9
0x34b655…2a6f
6 touches
3 conflicts
0x5150abbe…43c3
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity