← previous blocknext block →recent activity
Analyzing
Block #100,577,503
19 transactions · 18 stateful · 2026-08-30 21:30:31 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,577,503 · 19 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
1w02w13w24w35w06w110w011w114w215w316w017w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x56a919c4…ab49
0xee8c0e…1242
6 touches
3 conflicts
0x729c91b8…9537
0x188d58…ea8e
6 touches
3 conflicts
0x729c91b8…9538
0x188d58…ea8e
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x820d7282…6c34
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
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 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity