← previous blocknext block →recent activity
Analyzing
Block #100,055,007
24 transactions · 20 stateful · 2026-08-29 01:37:16 UTC
Parallelism
83/100
Blocked
30%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,055,007 · 24 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
2w05w06w111w012w114w216w322w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2fab62fb…a7c9
0x34b655…2a6f
8 touches
6 conflicts
0xb240b520…a88a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x3ab3047d…d183
0x40c49f…2af0
4 touches
1 conflict
0x0e4fa697…08ca
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4ec9ff52…e6f7
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
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 0x2fab62fbc2…4ea7c9
Audit this contract →
← previous block·next block →recent activity