← previous blocknext block →recent activity
Analyzing
Block #100,161,302
12 transactions · 12 stateful · 2026-08-29 10:32:35 UTC
Parallelism
75/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,161,302 · 12 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
5w06w07w18w211w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3b6ff206…614f
0x8964d7…10f8
6 touches
3 conflicts
0x3b6ff206…614e
0x8964d7…10f8
6 touches
3 conflicts
0x3b6ff206…614b
0x8964d7…10f8
6 touches
3 conflicts
0x2a07e64e…fe77
0x754704…b603
6 touches
3 conflicts
0x00000000…0008
0x8964d7…10f8
6 touches
3 conflicts
0x3b6ff206…614a
0x8964d7…10f8
6 touches
3 conflicts
0x3b6ff206…6151
0x8964d7…10f8
6 touches
3 conflicts
0x3fde77e8…63f8
0x8964d7…10f8
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: 0x8964d7c9…5b10f8
3 conflicts on slot 0x3b6ff206ce…bd614f
Audit this contract →
← previous block·next block →recent activity