← previous blocknext block →recent activity
Analyzing
Block #100,234,439
18 transactions · 18 stateful · 2026-08-29 16:40:43 UTC
Parallelism
56/100
Blocked
56%
Avg conflicts / tx
1.78
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,234,439 · 18 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
1w04w05w16w07w18w010w111w212w313w414w515w216w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0x53e5a520…5aac
0x34b655…2a6f
10 touches
10 conflicts
0x8db32935…81a7
0x34b655…2a6f
10 touches
10 conflicts
0x3e6302c8…64f5
0x34b655…2a6f
6 touches
3 conflicts
0x89ac61bf…9443
0x34b655…2a6f
6 touches
3 conflicts
0x1d17ba18…e2f1
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity