← previous blocknext block →recent activity
Analyzing
Block #100,920,202
23 transactions · 16 stateful · 2026-09-01 02:14:48 UTC
Parallelism
83/100
Blocked
56%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,920,202 · 23 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
1w03w17w09w111w012w013w114w215w116w217w318w019w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06ebe7df…5755
0x8964d7…10f8
6 touches
3 conflicts
0x70739d72…d16f
0x8964d7…10f8
6 touches
3 conflicts
0x70739d72…d16d
0x8964d7…10f8
6 touches
3 conflicts
0x70739d72…d16c
0x8964d7…10f8
6 touches
3 conflicts
0x06ebe7df…5757
0x8964d7…10f8
6 touches
3 conflicts
0x18a9b62d…d89e
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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 0x06ebe7df71…e45755
Audit this contract →
← previous block·next block →recent activity