← previous blocknext block →recent activity
Analyzing
Block #74,351,232
24 transactions · 22 stateful · 2026-05-13 15:54:01 UTC
Parallelism
83/100
Blocked
45%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,351,232 · 24 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
1w02w13w27w310w012w113w214w318w319w122w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x908d4442…2c4b
0x34b655…2a6f
6 touches
3 conflicts
0x99f080dc…58c1
0x34b655…2a6f
6 touches
3 conflicts
0xa54d4519…267f
0x34b655…2a6f
6 touches
3 conflicts
0x1952c598…df64
0x34b655…2a6f
6 touches
3 conflicts
0x62d080e9…4a7c
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x8c49c85c…ee96
0x34b655…2a6f
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: Perpl
6 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity