← previous blocknext block →recent activity
Analyzing
Block #100,143,988
21 transactions · 19 stateful · 2026-08-29 09:05:25 UTC
Parallelism
81/100
Blocked
37%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,143,988 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w110w011w112w113w217w318w019w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x759da569…17d9
0x8964d7…10f8
6 touches
3 conflicts
0x102a468a…beb5
0x8964d7…10f8
6 touches
3 conflicts
0x759da569…17d2
0x8964d7…10f8
6 touches
3 conflicts
0x759da569…17d3
0x8964d7…10f8
6 touches
3 conflicts
0x759da569…17d6
0x8964d7…10f8
6 touches
3 conflicts
0x759da569…17d7
0x8964d7…10f8
6 touches
3 conflicts
0xa1616198…661f
0x34b655…2a6f
6 touches
3 conflicts
0xa169711f…c7f3
0x34b655…2a6f
6 touches
3 conflicts
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 0x759da56946…7c17d9
Audit this contract →
← previous block·next block →recent activity