← previous blocknext block →recent activity
Analyzing
Block #100,587,682
22 transactions · 19 stateful · 2026-08-30 22:21:43 UTC
Parallelism
73/100
Blocked
58%
Avg conflicts / tx
1.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,587,682 · 22 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
1w02w13w24w38w19w210w312w414w415w516w317w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5bec32a…b8c3
0x34b655…2a6f
12 touches
15 conflicts
0xaf529aa6…4bae
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0xe5060fe3…ebe9
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001e
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
8 touches
6 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
15 conflicts on slot 0xd5bec32a69…cbb8c3
Audit this contract →
← previous block·next block →recent activity