← previous blocknext block →recent activity
Analyzing
Block #100,877,435
13 transactions · 11 stateful · 2026-08-31 22:39:41 UTC
Parallelism
77/100
Blocked
36%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,877,435 · 13 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
1w02w03w18w19w212w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf38a3927…ad62
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6bea7638…9624
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd9722304…6ed0
0x34b655…2a6f
4 touches
1 conflict
0xe2d8f1b3…f6ac
0x34b655…2a6f
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
2 touches
0 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
3 conflicts on slot 0xf38a392760…8fad62
Audit this contract →
← previous block·next block →recent activity