← previous blocknext block →recent activity
Analyzing
Block #100,227,694
15 transactions · 13 stateful · 2026-08-29 16:06:46 UTC
Parallelism
80/100
Blocked
23%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,227,694 · 15 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
1w09w012w113w214w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb20094ed…0fef
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xef048f92…572b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0xc13e1d5c…62c6
0x34b655…2a6f
4 touches
1 conflict
0xc40fa8a7…a319
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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 0xb20094edc6…ed0fef
Audit this contract →
← previous block·next block →recent activity