← previous blocknext block →recent activity
Analyzing
Block #100,793,620
22 transactions · 16 stateful · 2026-08-31 15:37:51 UTC
Parallelism
86/100
Blocked
38%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,793,620 · 22 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
1w03w04w16w07w28w115w016w119w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x637d9a29…f9bb
0x34b655…2a6f
6 touches
3 conflicts
0xf984d8ab…6e4f
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x3ee8b564…4c49
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4f4bdabd…ffba
0x34b655…2a6f
4 touches
1 conflict
0x699ee60f…de01
0x34b655…2a6f
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 0x637d9a29be…2bf9bb
Audit this contract →
← previous block·next block →recent activity