← previous blocknext block →recent activity
Analyzing
Block #100,858,989
20 transactions · 18 stateful · 2026-08-31 21:06:54 UTC
Parallelism
85/100
Blocked
50%
Avg conflicts / tx
0.65
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,858,989 · 20 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
2w03w14w26w07w08w19w010w111w212w113w215w016w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a100e05…c541
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x2f74f175…9287
0x34ae4d…3fc5
4 touches
1 conflict
0x2f74f175…9288
0x34ae4d…3fc5
4 touches
1 conflict
0x3ba7edbb…80e6
0x34ae4d…3fc5
4 touches
1 conflict
0x46279ae7…20dd
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
3 conflicts on slot 0x9a100e057a…2ac541
Audit this contract →
← previous block·next block →recent activity