← previous blocknext block →recent activity
Analyzing
Block #100,125,086
23 transactions · 22 stateful · 2026-08-29 07:30:06 UTC
Parallelism
61/100
Blocked
36%
Avg conflicts / tx
1.3
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #100,125,086 · 23 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
4w09w013w115w216w317w418w519w620w721w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xf3d10975…0d07
0x34b655…2a6f
10 touches
10 conflicts
0xb9868b52…c77f
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
6 touches
3 conflicts
0x7083c381…0ce7
0x34b655…2a6f
4 touches
1 conflict
0x7a672810…1732
0x34b655…2a6f
4 touches
1 conflict
0xb0f5d668…99ac
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity