← previous blocknext block →recent activity
Analyzing
Block #100,144,035
21 transactions · 20 stateful · 2026-08-29 09:05:39 UTC
Parallelism
48/100
Blocked
55%
Avg conflicts / tx
2.43
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #100,144,035 · 21 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w07w38w49w510w611w714w815w916w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
14 touches
21 conflicts
0x61571888…b392
0x34b655…2a6f
12 touches
15 conflicts
0xf95c3143…ac6d
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0xd2a76d80…ee44
0x34b655…2a6f
8 touches
6 conflicts
0x948836ff…59ab
0x34b655…2a6f
6 touches
3 conflicts
0x758a0dd5…0f46
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
36 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity