← previous blocknext block →recent activity
Analyzing
Block #75,893,596
9 transactions · 6 stateful · 2026-05-20 19:41:30 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,893,596 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x913d660d…82b4
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x7982ca1b…f8da
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x50c61506…343f
0x34b655…2a6f
3 touches
1 conflict
0x8a35acfb…d1a6
0x8d66a4…3095
3 touches
1 conflict
0x9abd5cd0…9d1d
0x8d66a4…3095
3 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
1 conflict on slot 0x913d660de4…fc82b4
Audit this contract →
← previous block·next block →recent activity