← previous blocknext block →recent activity
Analyzing
Block #100,728,526
22 transactions · 22 stateful · 2026-08-31 10:10:13 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.95
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,728,526 · 22 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
2w05w18w210w311w412w513w014w116w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7c360ad…e3d7
0x34b655…2a6f
12 touches
15 conflicts
0x382434ca…96b5
0x34b655…2a6f
10 touches
10 conflicts
0x19db4c1d…a025
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x2e1f5171…ad2d
0x34b655…2a6f
6 touches
3 conflicts
0x07da0a8b…965b
0x34b655…2a6f
4 touches
1 conflict
0x08e8f2c9…a11a
0x34b655…2a6f
4 touches
1 conflict
0x31d88d27…7617
0x34b655…2a6f
4 touches
1 conflict
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
15 conflicts on slot 0xc7c360adae…34e3d7
Audit this contract →
← previous block·next block →recent activity