← previous blocknext block →recent activity
Analyzing
Block #100,921,158
15 transactions · 15 stateful · 2026-09-01 02:19:37 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.73
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,921,158 · 15 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w19w210w311w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2827ae77…4368
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xb839a1e8…22b3
0x34b655…2a6f
6 touches
3 conflicts
0xf173d295…4e87
0x34b655…2a6f
6 touches
3 conflicts
0xf191067f…59ce
0x34b655…2a6f
6 touches
3 conflicts
0x3da1337e…9c84
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xa1ed1673…ecc0
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 0x2827ae778d…a84368
Audit this contract →
← previous block·next block →recent activity