← previous blocknext block →recent activity
Analyzing
Block #100,268,696
13 transactions · 11 stateful · 2026-08-29 19:34:38 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,268,696 · 13 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
2w04w08w19w010w211w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x83a29d51…c88d
0x40c49f…2af0
4 touches
1 conflict
0x23529e13…6f25
0x34b655…2a6f
4 touches
1 conflict
0x2827ae77…4368
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd0fd6c76…ddaf
0x34b655…2a6f
4 touches
1 conflict
0xd488e0a9…9bae
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
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: 0x40c49f17…d22af0
1 conflict on slot 0x83a29d5126…2ac88d
Audit this contract →
← previous block·next block →recent activity