← previous blocknext block →recent activity
Analyzing
Block #100,738,276
17 transactions · 14 stateful · 2026-08-31 10:59:15 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,738,276 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w09w110w211w312w413w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9722304…6ed0
0x34b655…2a6f
8 touches
6 conflicts
0xf21aeb71…92a2
0x34b655…2a6f
8 touches
6 conflicts
0x6f84ef84…787f
0x34b655…2a6f
6 touches
3 conflicts
0xd99d25df…ecd8
0x34b655…2a6f
4 touches
1 conflict
0x2c2761c0…476e
0x34b655…2a6f
4 touches
1 conflict
0x706c758c…2fdb
0x34b655…2a6f
4 touches
1 conflict
0x10d80fee…dbda
0x34ae4d…3fc5
2 touches
0 conflicts
0x40970e69…da50
0x34ae4d…3fc5
2 touches
0 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 0xd97223041d…366ed0
Audit this contract →
← previous block·next block →recent activity