← previous blocknext block →recent activity
Analyzing
Block #100,923,558
27 transactions · 19 stateful · 2026-09-01 02:31:41 UTC
Parallelism
85/100
Blocked
42%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,923,558 · 27 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w07w18w19w210w011w114w115w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd809bbec…baef
0x34b655…2a6f
8 touches
6 conflicts
0x19795ad6…4a16
0x34b655…2a6f
6 touches
3 conflicts
0xf2410d5d…8153
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xe098738f…9bbe
0x34b655…2a6f
6 touches
3 conflicts
0x1bb6d1d5…5997
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x2924fbfa…b72b
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
6 conflicts on slot 0xd809bbec79…17baef
Audit this contract →
← previous block·next block →recent activity