← previous blocknext block →recent activity
Analyzing
Block #100,080,127
15 transactions · 15 stateful · 2026-08-29 03:43:44 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
0.87
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,080,127 · 15 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
1w02w17w09w110w211w212w313w414w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x177cb57c…07e4
0x34b655…2a6f
6 touches
3 conflicts
0xd96da669…cfd2
0x34b655…2a6f
6 touches
3 conflicts
0x51cfbcbc…fa29
0x34b655…2a6f
6 touches
3 conflicts
0xf98c943e…7c44
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xe483d4e3…e52f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…00c9
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity