← previous blocknext block →recent activity
Analyzing
Block #100,159,142
24 transactions · 22 stateful · 2026-08-29 10:21:42 UTC
Parallelism
63/100
Blocked
59%
Avg conflicts / tx
1.63
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #100,159,142 · 24 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
1w02w03w04w06w18w29w111w212w313w414w519w420w521w622w723w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x639be938…49c4
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xe71981fd…8d8c
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x191e0467…70e5
0x34b655…2a6f
8 touches
6 conflicts
0x676f9f01…a8ac
0x34b655…2a6f
6 touches
3 conflicts
0x08e8f2c9…a11a
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot 0x639be93840…0f49c4
Audit this contract →
← previous block·next block →recent activity