← previous blocknext block →recent activity
Analyzing
Block #72,232,938
19 transactions · 18 stateful · 2026-05-03 20:30:32 UTC
Parallelism
68/100
Blocked
56%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #72,232,938 · 19 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
2w04w05w16w07w18w29w310w112w214w215w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa02838a3…bc54
0x34b655…2a6f
10 touches
10 conflicts
0x35b65947…44d1
0xc8689a…ee79
8 touches
6 conflicts
0xfa2527aa…9dd5
0x34b655…2a6f
8 touches
6 conflicts
0xfadc118d…5d64
0x34b655…2a6f
8 touches
6 conflicts
0xfe3d37ee…6e67
0x34b655…2a6f
8 touches
6 conflicts
0xfffd94f5…e894
0x34b655…2a6f
8 touches
6 conflicts
0x005fb969…2d97
0x34b655…2a6f
8 touches
6 conflicts
0x17e2d2a0…359e
0x34b655…2a6f
8 touches
6 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: Perpl
10 conflicts on slot 0xa02838a385…ffbc54
Audit this contract →
← previous block·next block →recent activity