← previous blocknext block →recent activity
Analyzing
Block #73,595,200
25 transactions · 21 stateful · 2026-05-10 03:44:03 UTC
Parallelism
76/100
Blocked
48%
Avg conflicts / tx
0.96
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #73,595,200 · 25 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w38w09w110w013w015w116w118w220w421w524w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d0b2509…074d
0x3bd359…433a
10 touches
10 conflicts
0x17606ba6…1b6e
0x754704…b603
10 touches
10 conflicts
0xe6455d1f…1029
0x754704…b603
10 touches
10 conflicts
0x8240d70c…7c3b
0x34b655…2a6f
6 touches
3 conflicts
0xe75ce681…ba5f
0x188d58…ea8e
4 touches
1 conflict
0xe75ce681…ba61
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
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)
10 conflicts on slot 0x0d0b2509ae…4b074d
Audit this contract →
← previous block·next block →recent activity