← previous blocknext block →recent activity
Analyzing
Block #100,585,596
19 transactions · 18 stateful · 2026-08-30 22:11:13 UTC
Parallelism
84/100
Blocked
33%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,585,596 · 19 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
1w03w04w05w06w110w111w012w113w114w218w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfda3b445…e5c1
0x34b655…2a6f
6 touches
3 conflicts
0x5f0a01c3…8269
0x851145…3f07
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb349e09a…256e
0x34b655…2a6f
4 touches
1 conflict
0xb82f494f…db33
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
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 0xfda3b4456b…f8e5c1
Audit this contract →
← previous block·next block →recent activity