← previous blocknext block →recent activity
Analyzing
Block #100,046,750
22 transactions · 22 stateful · 2026-08-29 00:55:43 UTC
Parallelism
68/100
Blocked
41%
Avg conflicts / tx
1.32
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,046,750 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w09w110w211w312w414w515w616w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6cc43e52…1f90
0x34b655…2a6f
12 touches
15 conflicts
0x66bff517…eab2
0x34b655…2a6f
12 touches
15 conflicts
0xc3baa205…f26e
0x34b655…2a6f
10 touches
10 conflicts
0xb482658a…e4f5
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xdd73a9c0…73c1
0x34b655…2a6f
8 touches
6 conflicts
0x4f3a6b4a…3819
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
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
15 conflicts on slot 0x6cc43e5238…e01f90
Audit this contract →
← previous block·next block →recent activity