← previous blocknext block →recent activity
Analyzing
Block #100,126,900
20 transactions · 11 stateful · 2026-08-29 07:39:14 UTC
Parallelism
85/100
Blocked
36%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,126,900 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w18w09w114w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5060cdde…445d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0xd106eb58…b2b1
0x34b655…2a6f
6 touches
3 conflicts
0x675cb7a8…dba5
0x34b655…2a6f
6 touches
3 conflicts
0xfd9bfada…b65b
0x34b655…2a6f
5 touches
3 conflicts
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x51fc8795…1266
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
3 conflicts on slot 0x5060cdde9e…d4445d
Audit this contract →
← previous block·next block →recent activity