← previous blocknext block →recent activity
Analyzing
Block #100,790,010
31 transactions · 28 stateful · 2026-08-31 15:19:41 UTC
Parallelism
68/100
Blocked
61%
Avg conflicts / tx
1.39
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #100,790,010 · 31 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w09w010w111w114w215w318w120w421w527w629w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcaabb8d…d0ff
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0x485d2778…aa5c
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x2827ae77…4368
0x34b655…2a6f
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 0xfcaabb8d7b…a2d0ff
Audit this contract →
← previous block·next block →recent activity