← previous blocknext block →recent activity
Analyzing
Block #100,080,705
18 transactions · 17 stateful · 2026-08-29 03:46:39 UTC
Parallelism
56/100
Blocked
41%
Avg conflicts / tx
1.33
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,080,705 · 18 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
5w07w08w19w210w311w413w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d7bbd81…7cc6
0x34b655…2a6f
12 touches
15 conflicts
0xebe581d8…2696
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x33206d3d…8b20
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x2c2db8e9…fdc7
0x34b655…2a6f
6 touches
3 conflicts
0x1e814ad8…7ad2
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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
15 conflicts on slot 0x1d7bbd81bb…287cc6
Audit this contract →
← previous block·next block →recent activity