← previous blocknext block →recent activity
Analyzing
Block #74,240,337
20 transactions · 18 stateful · 2026-05-13 03:36:35 UTC
Parallelism
55/100
Blocked
61%
Avg conflicts / tx
1.8
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #74,240,337 · 20 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w07w18w29w310w411w512w617w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5de96bd3…c60c
0x34b655…2a6f
14 touches
21 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
12 touches
15 conflicts
0xaa3492db…3703
0x34b655…2a6f
12 touches
15 conflicts
0x8a85cf3d…2868
0x34b655…2a6f
12 touches
15 conflicts
0x9df8469b…89b3
0x34b655…2a6f
12 touches
15 conflicts
0x908d4442…2c4b
0x34b655…2a6f
12 touches
15 conflicts
0xc6417de0…2191
0xc8689a…ee79
10 touches
10 conflicts
0x32ee90db…decc
0x34b655…2a6f
10 touches
10 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
21 conflicts on slot 0x5de96bd34a…ecc60c
Audit this contract →
← previous block·next block →recent activity