← previous blocknext block →recent activity
Analyzing
Block #74,901,739
24 transactions · 19 stateful · 2026-05-16 05:10:58 UTC
Parallelism
79/100
Blocked
47%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,901,739 · 24 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
2w03w14w05w16w07w112w013w114w215w316w422w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0004
0x8d66a4…3095
6 touches
3 conflicts
0x9fc6ea79…e2dc
0x34b655…2a6f
6 touches
3 conflicts
0x220f4f84…15f8
0x34b655…2a6f
4 touches
1 conflict
0x313f2565…5b00
0x34b655…2a6f
4 touches
1 conflict
0x388e001a…7e04
0x34b655…2a6f
4 touches
1 conflict
0x4546ebad…b908
0x34b655…2a6f
4 touches
1 conflict
0x61ad45b1…15ac
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