← previous blocknext block →recent activity
Analyzing
Block #100,560,137
24 transactions · 21 stateful · 2026-08-30 20:03:10 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,560,137 · 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
1w02w05w06w08w112w116w117w218w119w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0xce10a9bf…32f3
0x34b655…2a6f
6 touches
3 conflicts
0x4762dc89…fddf
0x34b655…2a6f
6 touches
3 conflicts
0x0f764fe0…a7a2
0x34b655…2a6f
6 touches
3 conflicts
0x15ae3bf3…2507
0x34b655…2a6f
6 touches
3 conflicts
0x3df6122f…fba3
0x34b655…2a6f
6 touches
3 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 0xc824469a90…af641f
Audit this contract →
← previous block·next block →recent activity