← previous blocknext block →recent activity
Analyzing
Block #74,332,026
24 transactions · 16 stateful · 2026-05-13 13:46:22 UTC
Parallelism
83/100
Blocked
31%
Avg conflicts / tx
0.25
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,332,026 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w19w218w119w321w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f483049…3cc7
0x34b655…2a6f
6 touches
3 conflicts
0xfe39a1f7…8eb0
0x34b655…2a6f
4 touches
1 conflict
0x0c5811ce…dfd8
0x34b655…2a6f
4 touches
1 conflict
0x17cd1479…00bb
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1a7
0x8d66a4…3095
4 touches
1 conflict
0x37cfaf01…4a46
0x34b655…2a6f
4 touches
1 conflict
0x37d49489…9309
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
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
3 conflicts on slot 0x4f4830497d…d73cc7
Audit this contract →
← previous block·next block →recent activity