← previous blocknext block →recent activity
Analyzing
Block #100,141,105
19 transactions · 18 stateful · 2026-08-29 08:50:54 UTC
Parallelism
53/100
Blocked
61%
Avg conflicts / tx
1.68
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #100,141,105 · 19 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
1w03w04w15w16w27w28w310w411w514w615w716w817w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x29354600…7b17
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xa11b60f7…8e8b
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x1d9867ad…6d9a
0x34b655…2a6f
6 touches
3 conflicts
0x2bb0d58d…9dcf
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
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 0x293546009c…387b17
Audit this contract →
← previous block·next block →recent activity