← previous blocknext block →recent activity
Analyzing
Block #100,095,484
23 transactions · 23 stateful · 2026-08-29 05:01:03 UTC
Parallelism
57/100
Blocked
43%
Avg conflicts / tx
1.96
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #100,095,484 · 23 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w07w18w29w310w411w512w617w718w821w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1681c4c…5858
0x34b655…2a6f
16 touches
28 conflicts
0xf98c943e…7c44
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0x4e58deff…c5d0
0x34b655…2a6f
8 touches
6 conflicts
0x5ed1f9d0…fc7f
0x34b655…2a6f
8 touches
6 conflicts
0xb54c8ced…5b8c
0x34b655…2a6f
8 touches
6 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 0xe1681c4c2a…9d5858
Audit this contract →
← previous block·next block →recent activity