← previous blocknext block →recent activity
Analyzing
Block #100,023,601
23 transactions · 23 stateful · 2026-08-28 22:59:11 UTC
Parallelism
65/100
Blocked
48%
Avg conflicts / tx
1.3
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,023,601 · 23 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
1w02w14w05w17w210w011w112w213w314w415w517w618w222w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x172b0de5…980b
0x34b655…2a6f
10 touches
10 conflicts
0x511bafbb…15be
0x34b655…2a6f
10 touches
10 conflicts
0x31827e57…3bb5
0x34b655…2a6f
10 touches
10 conflicts
0x2c2db8e9…fdc7
0x34b655…2a6f
10 touches
10 conflicts
0xe1f7bc91…2751
0x34b655…2a6f
8 touches
6 conflicts
0x48b13e5e…3c2a
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
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
10 conflicts on slot 0x172b0de5b2…14980b
Audit this contract →
← previous block·next block →recent activity