← previous blocknext block →recent activity
Analyzing
Block #74,588,050
25 transactions · 17 stateful · 2026-05-14 18:16:53 UTC
Parallelism
76/100
Blocked
47%
Avg conflicts / tx
0.64
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #74,588,050 · 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
3w04w05w112w014w115w220w121w222w323w424w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xf853eb8e…4027
0x34b655…2a6f
6 touches
3 conflicts
0xa91c899f…6ee3
0x34b655…2a6f
6 touches
3 conflicts
0x6c44331f…9735
0x34b655…2a6f
4 touches
1 conflict
0x75f6889e…7f1e
0x34b655…2a6f
4 touches
1 conflict
0x7cbd466f…1700
0x34b655…2a6f
4 touches
1 conflict
0x83cde744…b76b
0x34b655…2a6f
4 touches
1 conflict
0x849f3e33…c095
0x34b655…2a6f
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: Perpl
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity