← previous blocknext block →recent activity
Analyzing
Block #100,161,322
14 transactions · 14 stateful · 2026-08-29 10:32:41 UTC
Parallelism
86/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,161,322 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w010w011w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3b6ff206…614a
0x8964d7…10f8
4 touches
1 conflict
0x3b6ff206…614b
0x8964d7…10f8
4 touches
1 conflict
0x3b6ff206…614e
0x8964d7…10f8
4 touches
1 conflict
0x3b6ff206…614f
0x8964d7…10f8
4 touches
1 conflict
0x3b6ff206…6151
0x8964d7…10f8
4 touches
1 conflict
0x3fde77e8…63f5
0x8964d7…10f8
4 touches
1 conflict
0x3fde77e8…63f6
0x8964d7…10f8
4 touches
1 conflict
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
1 conflict on slot 0x3b6ff206ce…bd614a
Audit this contract →
← previous block·next block →recent activity