← previous blocknext block →recent activity
Analyzing
Block #75,863,526
45 transactions · 39 stateful · 2026-05-20 16:21:22 UTC
Parallelism
71/100
Blocked
69%
Avg conflicts / tx
2.38
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #75,863,526 · 45 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w06w17w08w110w112w013w114w015w016w117w218w320w021w122w223w324w425w526w627w728w829w930w1036w437w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
26 touches
78 conflicts
0xa5bfbb45…1ee8
0x34b655…2a6f
10 touches
10 conflicts
0x0711ec2d…d973
0x34b655…2a6f
10 touches
10 conflicts
0xc6417de0…2191
0xc8689a…ee79
10 touches
10 conflicts
0xe54a1f6f…18f2
0x34b655…2a6f
10 touches
10 conflicts
0xd49762c9…1359
0x34b655…2a6f
10 touches
10 conflicts
0x578e7f66…1b56
0x34b655…2a6f
10 touches
10 conflicts
0x5728edaf…f1d4
0x34b655…2a6f
10 touches
10 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
78 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity