← previous blocknext block →recent activity
Analyzing
Block #100,130,869
15 transactions · 15 stateful · 2026-08-29 07:59:13 UTC
Parallelism
60/100
Blocked
60%
Avg conflicts / tx
0.87
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,130,869 · 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
1w02w13w16w27w39w210w311w212w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x019e6736…3f64
0x34b655…2a6f
8 touches
6 conflicts
0x172b0de5…980b
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x044844a0…7418
0x34b655…2a6f
6 touches
3 conflicts
0xfac61869…a560
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0x019e67360b…3e3f64
Audit this contract →
← previous block·next block →recent activity