← previous blocknext block →recent activity
Analyzing
Block #102,105,706
34 transactions · 22 stateful · 2026-09-05 05:47:46 UTC
Parallelism
88/100
Blocked
32%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,105,706 · 34 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
1w02w03w05w06w015w116w126w027w228w229w232w133w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcc1b459…f94f
0x3bd359…433a
6 touches
3 conflicts
0xa74cd79c…705a
0x405b63…7777
6 touches
3 conflicts
0x839c0c71…bada
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0000
0xaa5de1…d330
6 touches
3 conflicts
0x00000000…0002
0xaa5de1…d330
6 touches
3 conflicts
0x00000000…0003
0xaa5de1…d330
6 touches
3 conflicts
0x84381bfb…4e1e
0xd32edf…ff58
5 touches
3 conflicts
0x7e5ea60a…c4aa
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: Wrapped MON (WMON)
3 conflicts on slot 0xbcc1b45913…43f94f
Audit this contract →
← previous block·next block →recent activity