← previous blocknext block →recent activity
Analyzing
Block #100,132,737
23 transactions · 20 stateful · 2026-08-29 08:08:37 UTC
Parallelism
78/100
Blocked
55%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,132,737 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w27w08w19w111w212w213w115w216w317w219w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x316191c8…66c8
0x34b655…2a6f
8 touches
6 conflicts
0x9194f4a3…10b8
0x754704…b603
6 touches
3 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0000
0xfa32f9…f3f0
6 touches
3 conflicts
0x00000000…0001
0xfa32f9…f3f0
6 touches
3 conflicts
0x99f666e3…b2a2
0x3bd359…433a
6 touches
3 conflicts
0xac33ff75…077b
0xfa32f9…f3f0
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
6 conflicts on slot 0x316191c821…6a66c8
Audit this contract →
← previous block·next block →recent activity