← previous blocknext block →recent activity
Analyzing
Block #100,588,337
37 transactions · 31 stateful · 2026-08-30 22:25:01 UTC
Parallelism
81/100
Blocked
42%
Avg conflicts / tx
1.08
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,588,337 · 37 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
1w04w05w16w17w28w09w310w411w512w615w119w220w321w433w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0x0b1bae0f…fae8
0xd32edf…ff58
9 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xd5a25205…645d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xeea3aab7…29d3
0x065c9d…c394
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
21 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity