← previous blocknext block →recent activity
Analyzing
Block #74,409,826
14 transactions · 6 stateful · 2026-05-13 22:24:07 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,409,826 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x050a4348…907a
0x34b655…2a6f
4 touches
1 conflict
0xd49762c9…1359
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x62d080e9…4a7c
0x34b655…2a6f
4 touches
1 conflict
0x0711ec2d…d973
0x34b655…2a6f
2 touches
0 conflicts
0x44f26cbe…58c2
0x34b655…2a6f
2 touches
0 conflicts
0x57de3828…3fbb
0x34b655…2a6f
2 touches
0 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x050a4348b1…8c907a
Audit this contract →
← previous block·next block →recent activity