← previous blocknext block →recent activity
Analyzing
Block #100,228,575
9 transactions · 8 stateful · 2026-08-29 16:11:12 UTC
Parallelism
67/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,228,575 · 9 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
2w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c0c3e3f…5849
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x10a5a231…be40
0x34b655…2a6f
4 touches
1 conflict
0xdfce7dfe…5053
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x8ec95f2b…f4d7
0x34b655…2a6f
4 touches
1 conflict
0x1e737223…2278
0x34b655…2a6f
2 touches
0 conflicts
0x948836ff…59ab
0x34b655…2a6f
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 0x2c0c3e3f10…6c5849
Audit this contract →
← previous block·next block →recent activity