← previous blocknext block →recent activity
Analyzing
Block #100,630,492
29 transactions · 28 stateful · 2026-08-31 01:57:05 UTC
Parallelism
79/100
Blocked
43%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,630,492 · 29 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
1w02w13w25w06w07w18w311w012w313w114w216w319w121w425w026w128w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfdafaeb3…4b67
0x34b655…2a6f
10 touches
10 conflicts
0x898d9b8a…d1ef
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0x3bd55803…5d4f
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x74e485b1…d380
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
10 conflicts on slot 0xfdafaeb30d…754b67
Audit this contract →
← previous block·next block →recent activity