← previous blocknext block →recent activity
Analyzing
Block #100,851,742
19 transactions · 19 stateful · 2026-08-31 20:30:27 UTC
Parallelism
68/100
Blocked
53%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,851,742 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w15w06w19w111w212w314w415w217w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc8d572c…b27d
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xb05cd4f5…73d0
0x34ae4d…3fc5
4 touches
1 conflict
0xe2263bea…6a9e
0x34ae4d…3fc5
4 touches
1 conflict
0xe2263bea…6aa2
0x34ae4d…3fc5
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
6 conflicts on slot 0xfc8d572cb3…e5b27d
Audit this contract →
← previous block·next block →recent activity