← previous blocknext block →recent activity
Analyzing
Block #74,332,018
23 transactions · 14 stateful · 2026-05-13 13:46:18 UTC
Parallelism
74/100
Blocked
57%
Avg conflicts / tx
0.87
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #74,332,018 · 23 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
1w02w13w27w08w19w218w019w120w321w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xa91c899f…6ee3
0x34b655…2a6f
8 touches
6 conflicts
0x57de3828…3fbb
0x34b655…2a6f
6 touches
3 conflicts
0x5ffc25fa…b119
0x34b655…2a6f
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x0711ec2d…d973
0x34b655…2a6f
6 touches
3 conflicts
0x313f2565…5b00
0x34b655…2a6f
6 touches
3 conflicts
0xd49762c9…1359
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity