← previous blocknext block →recent activity
Analyzing
Block #100,062,478
24 transactions · 20 stateful · 2026-08-29 02:14:52 UTC
Parallelism
75/100
Blocked
50%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,062,478 · 24 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
1w02w13w04w16w28w09w113w214w315w420w121w523w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f46a4fb…3224
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0xfe39a1f7…8eb0
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0xcf6c1a79…b07f
0x34b655…2a6f
6 touches
3 conflicts
0x65067517…93f7
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 0x4f46a4fb0e…a43224
Audit this contract →
← previous block·next block →recent activity