← previous blocknext block →recent activity
Analyzing
Block #101,973,693
25 transactions · 22 stateful · 2026-09-04 18:38:28 UTC
Parallelism
80/100
Blocked
32%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,973,693 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w27w38w412w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36743f6f…476b
0x3bd359…433a
8 touches
6 conflicts
0xe31cf99d…cb66
0x754704…b603
6 touches
3 conflicts
0x09beabbc…065c
0x188d58…ea8e
4 touches
1 conflict
0x09beabbc…065e
0x188d58…ea8e
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x6af306bb…2e81
0x3bd359…433a
4 touches
1 conflict
0x7c403af1…31b1
0x3bd359…433a
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
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: Wrapped MON (WMON)
6 conflicts on slot 0x36743f6fc4…37476b
Audit this contract →
← previous block·next block →recent activity