← previous blocknext block →recent activity
Analyzing
Block #100,438,243
21 transactions · 20 stateful · 2026-08-30 09:49:52 UTC
Parallelism
62/100
Blocked
40%
Avg conflicts / tx
1.14
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,438,243 · 21 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
1w02w15w07w08w19w212w313w414w519w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x29cd05f5…390c
0x34b655…2a6f
8 touches
6 conflicts
0x8db32935…81a7
0x34b655…2a6f
8 touches
6 conflicts
0xf9874e36…beed
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x1244b105…8e9b
0x34b655…2a6f
6 touches
3 conflicts
0x7aa5d2c4…d6ef
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity