← previous blocknext block →recent activity
Analyzing
Block #100,434,084
26 transactions · 22 stateful · 2026-08-30 09:28:56 UTC
Parallelism
65/100
Blocked
45%
Avg conflicts / tx
1.35
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #100,434,084 · 26 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w313w415w516w618w720w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9711d76f…8e5c
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0xb3aa2022…9e09
0x34b655…2a6f
10 touches
10 conflicts
0xe9457301…83cd
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x69ee34d1…30f8
0x34b655…2a6f
6 touches
3 conflicts
0x4db508b8…b746
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
21 conflicts on slot 0x9711d76f96…cc8e5c
Audit this contract →
← previous block·next block →recent activity