← previous blocknext block →recent activity
Analyzing
Block #100,584,216
20 transactions · 19 stateful · 2026-08-30 22:04:17 UTC
Parallelism
55/100
Blocked
58%
Avg conflicts / tx
1.15
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #100,584,216 · 20 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w110w412w513w616w117w618w719w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8c46e40…fd23
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001e
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
8 touches
6 conflicts
0x75e73565…45fa
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
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
6 conflicts on slot 0xe8c46e40e0…a3fd23
Audit this contract →
← previous block·next block →recent activity