← previous blocknext block →recent activity
Analyzing
Block #74,346,206
16 transactions · 14 stateful · 2026-05-13 15:20:40 UTC
Parallelism
69/100
Blocked
50%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,346,206 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w06w17w08w19w211w113w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x050a4348…907a
0x34b655…2a6f
8 touches
6 conflicts
0x62d080e9…4a7c
0x34b655…2a6f
8 touches
6 conflicts
0x908d4442…2c4b
0x34b655…2a6f
8 touches
6 conflicts
0x6c44331f…9735
0x34b655…2a6f
6 touches
3 conflicts
0xf853eb8e…4027
0x34b655…2a6f
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0xd49762c9…1359
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
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 0x050a4348b1…8c907a
Audit this contract →
← previous block·next block →recent activity