← previous blocknext block →recent activity
Analyzing
Block #74,421,057
24 transactions · 21 stateful · 2026-05-13 23:38:44 UTC
Parallelism
63/100
Blocked
48%
Avg conflicts / tx
1.13
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #74,421,057 · 24 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
6w07w18w29w310w417w018w119w120w521w622w723w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x62d080e9…4a7c
0x34b655…2a6f
8 touches
6 conflicts
0xadac4a86…c2bc
0x34b655…2a6f
6 touches
3 conflicts
0x37d49489…9309
0x34b655…2a6f
4 touches
1 conflict
0x55b6a001…1e7a
0x34b655…2a6f
4 touches
1 conflict
0x57de3828…3fbb
0x34b655…2a6f
4 touches
1 conflict
0x5ce2465f…c4f1
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 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity