← previous blocknext block →recent activity
Analyzing
Block #85,172,401
30 transactions · 23 stateful · 2026-07-02 19:10:36 UTC
Parallelism
87/100
Blocked
48%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,172,401 · 30 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
2w03w14w25w37w19w310w011w117w018w019w120w221w222w124w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd025d7d7…f05a
0x3bd359…433a
8 touches
6 conflicts
0x90753351…c301
0xd32edf…ff58
7 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x01e7b865…6e6e
0x188d58…ea8e
4 touches
1 conflict
0x36cd3056…b5d4
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
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 0xd025d7d72f…4df05a
Audit this contract →
← previous block·next block →recent activity