← previous blocknext block →recent activity
Analyzing
Block #100,567,345
21 transactions · 21 stateful · 2026-08-30 20:39:25 UTC
Parallelism
71/100
Blocked
43%
Avg conflicts / tx
0.57
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,567,345 · 21 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
1w02w15w16w010w212w013w115w216w117w318w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f89b4b9…2478
0x34b655…2a6f
6 touches
3 conflicts
0x9a100e05…c541
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c5
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x109d8a52…a7b7
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 0x6f89b4b9ef…ef2478
Audit this contract →
← previous block·next block →recent activity