← previous blocknext block →recent activity
Analyzing
Block #100,917,896
26 transactions · 24 stateful · 2026-09-01 02:03:12 UTC
Parallelism
73/100
Blocked
58%
Avg conflicts / tx
1.15
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,917,896 · 26 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w26w49w011w112w213w415w516w617w318w420w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc9915b5…542c
0x34b655…2a6f
10 touches
10 conflicts
0x5fd4ecd5…2ef0
0x34b655…2a6f
10 touches
10 conflicts
0xc01a724e…f883
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0xd53220ed…4739
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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
10 conflicts on slot 0xdc9915b513…2b542c
Audit this contract →
← previous block·next block →recent activity