← previous blocknext block →recent activity
Analyzing
Block #100,103,854
27 transactions · 26 stateful · 2026-08-29 05:43:11 UTC
Parallelism
63/100
Blocked
58%
Avg conflicts / tx
1.63
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #100,103,854 · 27 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w05w17w18w29w311w114w215w116w317w418w222w523w624w725w826w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x65021fef…b735
0xa6afd3…d132
6 touches
3 conflicts
0x92f41d1f…4258
0xa6afd3…d132
6 touches
3 conflicts
0x92385428…6941
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity