← previous blocknext block →recent activity
Analyzing
Block #100,585,566
17 transactions · 16 stateful · 2026-08-30 22:11:04 UTC
Parallelism
82/100
Blocked
13%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,585,566 · 17 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
6w07w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b10f1de…fc43
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xad3e66be…dccc
0xc8689a…ee79
4 touches
1 conflict
0x6433984e…7951
0x34b655…2a6f
4 touches
1 conflict
0x68c07cb9…ae14
0x34b655…2a6f
4 touches
1 conflict
0xb51a7ce8…5102
0x34b655…2a6f
4 touches
1 conflict
0xba931867…ec74
0x34b655…2a6f
4 touches
1 conflict
0xc4feec13…d1b9
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 0x0b10f1de2a…acfc43
Audit this contract →
← previous block·next block →recent activity