← previous blocknext block →recent activity
Analyzing
Block #100,587,776
21 transactions · 17 stateful · 2026-08-30 22:22:11 UTC
Parallelism
86/100
Blocked
35%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,587,776 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w18w09w110w011w116w217w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4c6da38…3a6a
0x34b655…2a6f
6 touches
3 conflicts
0xfcc8f826…7c5f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x97dd7f86…83fd
0x40c49f…2af0
6 touches
3 conflicts
0x09215eca…8799
0x40c49f…2af0
5 touches
3 conflicts
0x59658b83…222b
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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
3 conflicts on slot 0xa4c6da388f…913a6a
Audit this contract →
← previous block·next block →recent activity