← previous blocknext block →recent activity
Analyzing
Block #72,282,916
23 transactions · 17 stateful · 2026-05-04 02:06:23 UTC
Parallelism
70/100
Blocked
41%
Avg conflicts / tx
0.7
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #72,282,916 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w311w412w513w014w117w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17606ba6…1b6e
0x754704…b603
10 touches
10 conflicts
0xe75ce681…ba5f
0x188d58…ea8e
8 touches
6 conflicts
0xe75ce681…ba60
0x188d58…ea8e
8 touches
6 conflicts
0x3639e293…f1cf
0xd32edf…ff58
7 touches
6 conflicts
0xf91b744e…9117
0x754704…b603
6 touches
3 conflicts
0x6af306bb…2e81
0x3bd359…433a
6 touches
3 conflicts
0x1c354dc0…96de
0x754704…b603
6 touches
3 conflicts
0x0dbf9688…c6cf
0xd18b7e…414b
6 touches
3 conflicts
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: USDC (USDC)
10 conflicts on slot 0x17606ba612…ea1b6e
Audit this contract →
← previous block·next block →recent activity