← previous blocknext block →recent activity
Analyzing
Block #100,155,397
24 transactions · 23 stateful · 2026-08-29 10:02:50 UTC
Parallelism
67/100
Blocked
52%
Avg conflicts / tx
1.92
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,155,397 · 24 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
1w02w03w16w07w18w29w310w411w513w515w116w218w620w723w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc8328065…611a
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x5ed1f9d0…fc7f
0x34b655…2a6f
12 touches
15 conflicts
0xd66696e0…0842
0x34b655…2a6f
10 touches
10 conflicts
0x1fe1380c…bf26
0x34b655…2a6f
8 touches
6 conflicts
0xf164c200…9494
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
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 0xc83280654f…70611a
Audit this contract →
← previous block·next block →recent activity