← previous blocknext block →recent activity
Analyzing
Block #100,080,548
22 transactions · 20 stateful · 2026-08-29 03:45:51 UTC
Parallelism
64/100
Blocked
55%
Avg conflicts / tx
1.5
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,080,548 · 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
1w02w13w05w17w011w112w213w314w415w516w617w121w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6a0aea7…a426
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x42e917f7…ed8c
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xa11b60f7…8e8b
0x34b655…2a6f
8 touches
6 conflicts
0x97559ec1…f88c
0x34b655…2a6f
6 touches
3 conflicts
0xd895ee0b…d301
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
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
15 conflicts on slot 0xc6a0aea730…e4a426
Audit this contract →
← previous block·next block →recent activity