← previous blocknext block →recent activity
Analyzing
Block #74,289,719
14 transactions · 14 stateful · 2026-05-13 09:04:54 UTC
Parallelism
50/100
Blocked
43%
Avg conflicts / tx
1.29
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #74,289,719 · 14 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w27w38w49w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
12 touches
15 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
8 touches
6 conflicts
0xddf0e471…ce9d
0x34b655…2a6f
8 touches
6 conflicts
0x1bc9b1ca…85ef
0x34b655…2a6f
8 touches
6 conflicts
0xafd59af5…5257
0xc8689a…ee79
6 touches
3 conflicts
0x34ea716f…4c40
0x34b655…2a6f
6 touches
3 conflicts
0x78e901bc…b1df
0x34b655…2a6f
6 touches
3 conflicts
0x94710b77…a921
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
15 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity