← previous blocknext block →recent activity
Analyzing
Block #75,199,655
19 transactions · 15 stateful · 2026-05-17 14:21:04 UTC
Parallelism
74/100
Blocked
40%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #75,199,655 · 19 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
1w02w15w06w07w18w29w310w416w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0x7b97d40a…09ed
0x34b655…2a6f
4 touches
1 conflict
0xd49762c9…1359
0x34b655…2a6f
4 touches
1 conflict
0xedb848fe…6534
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xc6417de0…2191
0xc8689a…ee79
4 touches
1 conflict
0x58339bfb…d0df
0x065c9d…c394
4 touches
1 conflict
0x57de3828…3fbb
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