← previous blocknext block →recent activity
Analyzing
Block #100,809,164
38 transactions · 36 stateful · 2026-08-31 16:56:04 UTC
Parallelism
66/100
Blocked
67%
Avg conflicts / tx
2.26
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #100,809,164 · 38 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w16w27w28w39w411w212w313w414w522w523w128w229w430w534w937w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x54c6fb44…369a
0x34b655…2a6f
10 touches
10 conflicts
0x0b3eb43a…ca08
0x34b655…2a6f
8 touches
6 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xa293b33b…5acd
0x34b655…2a6f
6 touches
3 conflicts
0xa81533d7…e23f
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity