← previous blocknext block →recent activity
Analyzing
Block #100,104,028
29 transactions · 25 stateful · 2026-08-29 05:44:03 UTC
Parallelism
72/100
Blocked
64%
Avg conflicts / tx
1.48
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,104,028 · 29 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w211w012w113w214w315w018w123w424w325w526w627w728w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0xf3d10975…0d07
0x34b655…2a6f
10 touches
10 conflicts
0x631b4113…baa9
0x34b655…2a6f
10 touches
10 conflicts
0xf0499c38…de2a
0xd32edf…ff58
9 touches
10 conflicts
0xba5743c7…21c3
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x52e0faa1…d718
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
10 conflicts on slot 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity