← previous blocknext block →recent activity
Analyzing
Block #102,040,253
28 transactions · 23 stateful · 2026-09-05 00:15:49 UTC
Parallelism
86/100
Blocked
48%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,040,253 · 28 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
1w03w15w16w17w08w19w112w017w219w221w322w123w225w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x997ccc40…4dfd
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0003
0xf5b5f7…6d70
6 touches
3 conflicts
0xa8f94882…8565
0xd32edf…ff58
5 touches
3 conflicts
0x0db691ab…3ee3
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x4d1e3e31…edf8
0x3bd359…433a
4 touches
1 conflict
0x8e485ef0…8a8a
0x3bd359…433a
4 touches
1 conflict
0x13477596…b14c
0x754704…b603
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)
3 conflicts on slot 0x997ccc40ce…804dfd
Audit this contract →
← previous block·next block →recent activity